cfg80211_next_nan_dw_notif(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ cfg80211_next_nan_dw_notif β€” Kernel API Manual ✨

okay so bestie, welcome to the tea on cfg80211_next_nan_dw_notif(9) πŸ’… this one lives in the Kernel API Manual and honestly? she's short but she matters, so let's not do her dirty.


🌸 NAME 🌸

cfg80211_next_nan_dw_notif β€” literally the function that notifies about the next NAN Discovery Window (DW) πŸ¦‹ no cap, that's the whole vibe of her.


πŸŽ€ SYNOPSIS πŸŽ€

void cfg80211_next_nan_dw_notif (struct wireless_dev *wdev , struct ieee80211_channel *chan , gfp_t gfp );

she returns void, meaning she gives you nothing back β€” she's not here for a return value, she's here to send a notification and dip ✨ main character energy fr.


πŸ‘‘ ARGUMENTS πŸ‘‘

three lil besties walk into the function, let's meet them 🫢

  • wdev β€” pointer to the wireless device structure. that's your wireless device, your whole wifi situation, the girl everything revolves around πŸ’–
  • chan β€” the DW channel. and listen, she's picky: it's 6, 44, or 149 β€” those are the options, iykyk πŸ”₯
  • gfp β€” the memory allocation flags. yes those flags, the allocation flavour, the gfp of it all 🧚

πŸ’€ reminder bestie: chan isn't a free-for-all β€” it's 6, 44 or 149. don't get creative, she will not slay with anything else.

more parts coming, stay tuned πŸ’œ

πŸ’… SEE ALSO πŸ’…

okay bestie, buckle up. this is the part where the manpage dumps everything it's ever dated β€” like a group chat member list where everyone brought a friend. every single one of these is a real (9) reference, i'm not making any of them up, and yes, you're gonna scroll. no cap. 🫢

first up, the source of truth + your starter pack:

that last one is lowkey the vibe check for your frequency limits, iykyk ✨


actions & configuration β€” the whole clique πŸŽ€


scanning & BSS list handling β€” where the tea gets collected πŸ“

  • 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)

NAN girlies rise πŸ‘‘ β€” and yes, since you're literally reading the NAN page, this section is your home turf:

  • Neighbor Awareness Networking (NAN)(9)
  • struct cfg80211_nan_band_config(9)
  • struct cfg80211_nan_conf(9)
  • struct cfg80211_nan_channel(9)
  • struct cfg80211_nan_local_sched(9)
  • struct cfg80211_nan_peer_map(9)
  • struct cfg80211_nan_peer_sched(9)
  • enum cfg80211_nan_conf_changes(9)
  • struct cfg80211_nan_func_filter(9)
  • struct cfg80211_nan_func(9)

the big struct energy section β€” main character structs only πŸ’€

the way wiphy_lock and wiphy_unlock are RIGHT THERE next to each other... iconic pairing behavior, honestly 🫢


utility functions β€” the little helpers that ate 🌸


data path helpers β€” where the actual packets do their little walk πŸ¦‹

ngl the find_* family is giving "i have 400 cousins and they're all invited to the function" 😭


regulatory enforcement infrastructure β€” the rules girlies πŸ’…

and then the notification/event squad, back to back, no breaks:


RFkill integration β€” press the button, feel something πŸ”₯

Vendor commands β€” special guest appearances unlocked πŸŽ€

Test mode β€” do NOT ship this energy πŸ™ˆ


the long tail of connection / notification helpers β€” they're all here, i promise, every single one ⭐

and that's the whole SEE ALSO wall, bestie β€” every last reference accounted for, nothing skipped, nothing merged, nothing invented πŸ’–

okay but we are so not done, hold that thought β€” there's more page coming and you're gonna want to be seated for it πŸ’…βœ¨

...and the cross-references keep coming, bestie, because this page is connected to literally everyone in the wireless group chat πŸ’… Here's the rest of the crew, all still indexed under 9 (kernel API section, iykyk):


okay that's literally the whole roster 🌈 Sixty-three cross-refs and not a single one skipped, because we don't do "etc." in this house. Every single one of those is a real page in the kernel API docs (section 9), so go click around, get lost in the lore, have a little hyperfixation moment πŸ¦‹

Quick vibe check, bestie: everything in these three parts came straight from the page β€” I didn't invent a single function, flag, or fact. If something's not listed above, it just isn't in this manual page πŸ’–

And that's a wrap on the whole thing! This lil masterpiece lives over in ./include/net, dated October 2026, and it goes by cfg80211_next_nan_dw_notif(9) β€” the one and only, the main character of her own manpage πŸ‘‘βœ¨ Thanks for reading all three parts, you icon. Go touch some grass (the kernel kind, obviously) πŸŒΈπŸ’œ

πŸ“¦ where this page comes from