ieee80211_scan_completed(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

okay bestie, welcome to the ieee80211_scan_completed(9) glow-up β€” this is the Kernel API Manual page for the function that tells mac80211 "bestie, the hardware scan is DONE." yw. ✨


πŸ¦‹ SYNOPSIS πŸ¦‹

void ieee80211_scan_completed (struct ieee80211_hw *hw , struct cfg80211_scan_info *info );

no cap, that's the whole signature. two pointers, zero drama. πŸ‘‘


🌸 ARGUMENTS 🌸

  • hw β€” the hardware that finished the scan. yes, that hardware. your little wifi guy. it did the scan and now it's reporting back 🫢
  • info β€” information about the completed scan. the receipts. the details. the "here's what happened while I was out" πŸ“‹

✨ DESCRIPTION ✨

so here's the vibe check: when hardware scan offload is used (like, when the hw_scan callback is assigned), this function needs to be called by the driver to notify mac80211 that the scan finished. that's it. that's the whole job. the driver hits up ieee80211_scan_completed() and mac80211 goes "omg thank u, noted." πŸ’…

and the truly iconic part? this function can be called from any context, including hardirq context. literally any context. hardirq included. no cap, no restrictions, no "sorry bestie you're in the wrong context" energy. 🌈


πŸŽ€ SEE ALSO πŸŽ€

the main character himself: kernel file ./include/net/mac80211.h. and now… the entire friend group. we're listing everybody, bestie, nobody gets left out. 🫢


and that's the whole page bestie!! scan complete, vibes immaculate, call it from hardirq context if u want, i don't make the rules (i do, actually, and the rule is: no cap) πŸ’…βœ¨

this cutie came out of ./include/net, dated October 2026, and she's filed under ieee80211_scan_completed(9) β€” go forth and notify mac80211, queen πŸŽ€πŸ‘‘πŸ¦‹

πŸ“¦ where this page comes from