cfg80211_sched_scan_results(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ cfg80211_sched_scan_results(9) ✨

okay so bestie, welcome to cfg80211_sched_scan_results β€” it lives in section 9 of the kernel API manual (yes, section 9, the kernel-internals one, we're in deep πŸ’…). the whole point of this function is literally just to spread the word: new scan results are here, come get 'em. it's giving "hey bestie the results are in" energy, and honestly? iconic.


πŸ“› NAME πŸ“›

cfg80211_sched_scan_results β€” notify that new scan results are available πŸŽ€

like, that's the entire job. you call it, you tell the world (well, the kernel) that a fresh batch of scheduled scan results has landed. no cap.


πŸ¦‹ SYNOPSIS πŸ¦‹

void cfg80211_sched_scan_results(struct wiphy *wiphy, u64 reqid);

yup, that's it β€” returns void, so don't go looking for a return value, there isn't one, it's not that kind of function 🫢


🌸 ARGUMENTS 🌸

  • wiphy β€” the wiphy which got scheduled scan results ✨ this is the wireless device thang that actually received the goodies, and you're passing it in so everyone knows who got lucky.
  • reqid β€” identifier for the related scheduled scan request πŸ’« it's the little tag that says "yeah, these results belong to that specific request," so nothing gets mixed up. a u64, because we're extra like that.

✨ SEE ALSO ✨

okay bestie, this is the part where the page just… introduces you to everyone. like the entire friend group. no cap, this is the biggest SEE ALSO to ever SEE ALSO, and every single one of these is a real cross-reference you can go look up πŸ’… so buckle up, we're doing roll call πŸŽ€

the whole roster lives in the kernel file ./include/net/cfg80211.h β€” that's the mothership, that's the group chat admin πŸ’–

like, that's just the capabilities crowd, and we're barely warmed up 😭

the configuration girlies. obsessed with all of them, genuinely 🫢

  • Scanning and BSS list handling(9)
  • struct cfg80211_ssid(9)
  • struct cfg80211_scan_info(9)
  • struct cfg80211_scan_6ghz_params(9)
  • struct cfg80211_scan_request(9)
  • struct cfg80211_match_set(9)
  • struct cfg80211_sched_scan_plan(9)
  • struct cfg80211_bss_select_adjust(9)
  • struct cfg80211_sched_scan_request(9)
  • enum cfg80211_signal_type(9)
  • struct cfg80211_inform_bss(9)
  • struct cfg80211_bss_ies(9)
  • struct cfg80211_bss(9)
  • ieee80211_bss_get_elem(9)
  • ieee80211_bss_get_ie(9)
  • struct cfg80211_auth_request(9)
  • struct cfg80211_assoc_link(9)
  • struct cfg80211_ml_reconf_req(9)
  • enum cfg80211_assoc_req_flags(9)
  • struct cfg80211_assoc_request(9)
  • struct cfg80211_deauth_request(9)
  • struct cfg80211_disassoc_request(9)
  • struct cfg80211_ibss_params(9)
  • struct cfg80211_bss_selection(9)
  • struct cfg80211_connect_params(9)
  • enum cfg80211_connect_params_changed(9)
  • enum wiphy_params_flags(9)
  • struct cfg80211_pmksa(9)
  • struct cfg80211_pkt_pattern(9)
  • struct cfg80211_wowlan_tcp(9)
  • struct cfg80211_wowlan(9)
  • struct cfg80211_coalesce_rules(9)
  • struct cfg80211_coalesce(9)
  • struct cfg80211_wowlan_nd_match(9)
  • struct cfg80211_wowlan_nd_info(9)
  • struct cfg80211_wowlan_wakeup(9)
  • struct cfg80211_gtk_rekey_data(9)
  • struct cfg80211_update_ft_ies_params(9)
  • struct cfg80211_mgmt_tx_params(9)
  • struct cfg80211_dscp_exception(9)
  • struct cfg80211_dscp_range(9)
  • struct cfg80211_qos_map(9)

scanning + BSS handling is literally the main character energy of this whole list, no notes πŸ’…

the entire wiphy family showing up together?? it's giving family reunion πŸŽ€

the "find" functions are the search bar of this whole ecosystem, iykyk πŸ”βœ¨

the regulatory girlies are internal but they still ate πŸ’€

vendor commands and test mode right next to each other, bestie that's a COLLAB 🌈

and that's the roll call, bestie β€” every single name verbatim, every single one searchable, nothing skipped, nothing merged πŸ˜€πŸ’–

okay bestie, the SEE ALSO list is genuinely a whole friend group, so buckle in β€” the rest of it goes like this πŸ’…


and that's the whole page, bestie, we literally made it 🌈 this came out of ./include/net, dated October 2026, and it's the page for cfg80211_sched_scan_results(9) β€” screenshot it, cite it, cite your sources, mwah πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from