hwrm_req_flags(9)

📦 version 7.3.1, in nixpkgs unstable

💅 hwrm_req_flags(9) — kernel API manual, bestie edition 🎀

okay so real talk, this is a page from the Kernel API Manual and it's about hwrm_req_flags(9), a tiny little function that's lowkey the vibe-setter for your HWRM requests ✨ she doesn't send anything herself, she just sets the mood before hwrm_req_send does its thing. main character energy honestly.

✨ NAME ✨

hwrm_req_flags — set the non-internal flags of the ctx 🫶

🌸 SYNOPSIS 🌸

void hwrm_req_flags (struct bnxt *bp , void *req , enum
       bnxt_hwrm_ctx_flags flags );

like literally that's it, that's the whole signature, no cap 💖

🦋 ARGUMENTS 🦋

  • bp — the driver context 🚗 iykyk, it's the bnxt thing you're working with
  • req — the request that's holding your HWRM command 📦
  • flags — the ctx flags that don't have BNXT_HWRM_INTERNAL_FLAG set 🙅‍♀️ those are not welcome here, bestie

👑 DESCRIPTION 👑

so the whole point of ctx flags is that callers use them to tell hwrm_req_send how to behave afterwards — it's giving "instruct the subsequent call" energy 💅

like, iconic examples:

  • callers can hit up hwrm_req_flags with BNXT_HWRM_CTX_SILENT to omit kernel prints of errors from hwrm_req_send 🤫 no drama in the logs, we love a quiet queen
  • or they can use BNXT_HWRM_FULL_WAIT to enforce hwrm_req_send waiting for the full timeout even if the FW is not responding 😭⏳ she will sit there and wait the whole time, respect

and the cute part? this is a generic function, so you can use it to set any flag that is not an internal flag of the HWRM module — periodt. ✨

🔥 SEE ALSO 🔥

kernel file: ./drivers/net/ethernet/broadcom/bnxt/bnxt_hwrm.c 📁 (go read her, she's the source of truth)

and her whole friend group, fr fr:

okay that's the whole page, mwah 💋 this came from ./drivers/net/ethernet/broadco... and it's dated October 2026 — go forth and set those flags, bestie, you're gonna slay 🌈👑

📦 where this page comes from