brcmf_p2p_n..._tx_complete(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… brcmf_p2p_n..._tx_complete πŸ’…

okay so real talk β€” this one comes straight out of the Kernel API Manual, section 9, and it's a tiny little callback with main character energy. no cap, it's short. but we're gonna read it properly anyway because that's just who we are. πŸŽ€


✨ NAME ✨

brcmf_p2p_notify_action_tx_complete β€” transmit action frame complete.

that's it. that's the whole vibe. your action frame got sent, and this is the little "yup, it's done bestie" moment that fires afterwards. obsessed. πŸ¦‹


🌸 SYNOPSIS 🌸

int brcmf_p2p_notify_action_tx_complete (struct brcmf_if *ifp , const
struct brcmf_event_msg *e , void *data );

it returns an int, it takes three things, and two of those three things are literally just vibes. we'll get there. πŸ’€


πŸ’– ARGUMENTS πŸ’–

  • ifp β€” interface control. it's the interface you're working with, that's the whole job. 🫢
  • e β€” event message. and here's the gag: it is not used at all. it's only hanging around so the signature stays usable for the fweh event dispatcher. so it's not lazy, it's structural. iykyk. 😭
  • data β€” not used. nothing. nope. nada. don't worry about it. πŸ™ˆ
like i said, two thirds of these arguments are just there to keep the shape of the function right. iconic behavior honestly. πŸ’…

🌈 SEE ALSO 🌈

if you wanna go digging (and you should, bestie), the actual source is chilling right here:

./drivers/net/wireless/broadcom/brcm80211/brcmfmac/p2p.c

and now, presenting… the entire friend group. every single one of them. no skipping, no cutting corners, we're doing the full roll call ✨:


like. forty-five references for one lil tx-complete callback? that's giving "knows everyone at the party" energy and honestly? respect. πŸ‘‘


anyway bestie, that's the page!! xoxo, this one dropped in October 2026, it lives under ./drivers/net/wireless/broadco..., and the footer is still out here going brcmf_p2p_n..._tx_complete(9) because some things never change. periodt. πŸ’œπŸŒΈ

πŸ“¦ where this page comes from