ieee80211_tx_status_irqsafe(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ieee80211_tx_status_irqsafe πŸ’…

okay so this is a page straight out of the Kernel API Manual, and bestie, it's a short one but it's important β€” it's the "yell at mac80211 from inside an interrupt" function. let's get into it 🫢


✨ NAME ✨

ieee80211_tx_status_irqsafe β€” the IRQ-safe transmit status callback. yes, "IRQ-safe" is doing a lot of heavy lifting in that name and it earned it πŸ’…


🌸 SYNOPSIS 🌸

void ieee80211_tx_status_irqsafe (struct ieee80211_hw *hw , struct
sk_buff *skb );

two args, no return value, that's the whole vibe. ✨


πŸ¦‹ ARGUMENTS πŸ¦‹

  • hw β€” the hardware that the frame was actually transmitted by, like, the physical device doing the radio thing πŸ“‘
  • skb β€” the frame that was transmitted. heads up though: after this call, it's owned by mac80211. not you. hand it over and let go, bestie πŸ™ˆ

πŸ’– DESCRIPTION πŸ’–

okay so it's basically like ieee80211_tx_status_skb but with a glow-up: you can call it in IRQ context. internally it defers to a tasklet, so it's not doing the spicy work right there in the interrupt β€” it's queuing it up and slaying later ⭐

🚨 vibe check / warning: calls to this function, ieee80211_tx_status_skb and ieee80211_tx_status_ni may not be mixed for a single hardware. like, pick one and commit. no cap, don't be switching it up mid-hardware πŸ’€

πŸ‘‘ SEE ALSO πŸ‘‘

the reading list is long bestie, but every single one is here, i promise. also peep the Kernel file ./include/net/mac80211.h πŸŽ€


and that's the whole page, bestie, we ate and left no crumbs πŸ’…βœ¨

signing off from ./include/net, dated October 2026, page ieee80211_tx_status_irqsafe(9) β€” mwah, go handle your interrupts responsibly πŸŽ€πŸ¦‹πŸ’–

πŸ“¦ where this page comes from