brcmf_p2p_no...ion_frame_rx(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… brcmf_p2p_notify_action_frame_rx(9) β€” a Kernel API Manual moment

okay so bestie, welcome to the Kernel API Manual (section 9, the fancy kernel-doc one), and today's main character is brcmf_p2p_notify_action_frame_rx(9). she's the one who catches action frames when they come in πŸŽ€


✨ NAME ✨

brcmf_p2p_notify_action_frame_rx β€” received action frame. that's it, that's the whole vibe πŸ¦‹


🌸 SYNOPSIS 🌸

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

look at her go 😭 three args, one int back, iconic behavior fr fr


🫢 ARGUMENTS 🫢

  • ifp β€” interfac control. (yes, "interfac" β€” that's literally what the manpage says, i don't make the rules πŸ’€)
  • e β€” event message. and here's the tea: it's not used, it's just there so the function is usable for the fweh event dispatcher. so it's giving "invited to the party but standing in the corner" πŸ™ˆ
  • data β€” payload of message, containing action frame data. this is the actual good stuff, the payload, the moment πŸ‘‘

πŸ‘‘ SEE ALSO πŸ‘‘

first up, the kernel file where she lives:

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

and now the whole extended friend group, no cap, every single one:

like, that's a whole squad 🧚 45 entries and we got through all of them, ate and left no crumbs πŸ”₯


ok tiny heads-up bestie: this one's a kernel-doc page, so no exit statuses, no env vars, no bugs section β€” that's just how she is. don't come for me πŸ’…

and that's the page!! sign-off time πŸŽ€ it came from ./drivers/net/wireless/broadco... (the source/version footer) and it's dated October 2026, which is so far away it's literally giving time traveler 😭 anyway ily, go read the rest of the brcmf_p2p_* family, mwah πŸ’–βœ¨

πŸ“¦ where this page comes from