__bnx2x_link_report(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay so bestie, welcome to the kernel API manual for __bnx2x_link_report β€” she's a bnx2x girlie and she's here to spill the tea about your link status 🌸


✨ NAME ✨

__bnx2x_link_report β€” literally the function whose whole job is report link status to OS. that's it, that's the vibe πŸ’…


πŸŽ€ SYNOPSIS πŸŽ€

void __bnx2x_link_report (struct bnx2x *bp );

no cap, that's the whole signature. she takes one (1) pointer and returns absolutely nothing back to you 😌


πŸ¦‹ ARGUMENTS πŸ¦‹

  • bp β€” the driver handle 🫢 like, your whole bnx2x situation lives in here.

🌈 DESCRIPTION 🌈

so here's the thing, bestie β€” this is a None atomic implementation. meaning: not atomic, do not be calling her from some atomic context thinking it's fine, because it is not fine πŸ™ˆ

🌟 she should be called under the phy_lock. that's not optional, that's the assignment. hold the lock, then report, iykyk πŸ”’

she reports the link status to the OS, and she does it exactly the way the driver needs her to. iconic behaviour, honestly πŸ‘‘


⭐ SEE ALSO ⭐

this is the part where we shout out her whole friend group πŸ’œ they all live in the kernel file ./drivers/net/ethernet/broadcom/bnx2x/bnx2x_cmn.c and honestly? the roster ate:

fr fr, go read all of them, they're all giving main character energy 🌟


πŸ’Œ before you go β€” this page came from source/version <code>./drivers/net/ethernet/broadco...</code> (yes bestie, it's truncated in the original, that's just how it is πŸ™ˆ) and it's dated October 2026. mwah, stay hydrated, hold your locks, and don't call non-atomic functions from atomic context πŸ’‹βœ¨

πŸ“¦ where this page comes from