cfg80211_nan_cluster_joined(9)

📦 version 7.3.1, in nixpkgs unstable

💖 cfg80211_nan_cluster_joined 💖

okay so bestie, we're in the cfg80211_nan_cluster_joined(9) zone — yes that (9) is the kernel API manual section, we're in the big leagues now 🫶. This one's short and sweet, so let's get into it.

✨ NAME ✨

cfg80211_nan_cluster_joined — the lil notification that goes "hey, we joined a NAN cluster!!" 📣

✨ SYNOPSIS ✨

void cfg80211_nan_cluster_joined (struct wireless_dev *wdev , const u8
*cluster_id , bool new_cluster , gfp_t gfp );

no cap, that's the whole signature. four args, one void return, zero drama 💅

✨ ARGUMENTS ✨

  • wdev — pointer to the struct wireless_dev, aka the wireless device structure. this is the main character of the operation 👑
  • cluster_id — the Cluster ID of the NAN cluster that was joined or started. const u8 * so bestie, you're not touching it 🔒
  • new_cluster — a bool that tells you if this is a brand-new cluster or an existing one. the vibe check: fresh 🌱 or already established 🏛️
  • gfp — the memory allocation flags (gfp_t). standard kernel allocation-flag situation, you know the drill 🧚

✨ DESCRIPTION ✨

so here's the tea 🍓 — this function is what you call to notify user space when a NAN cluster has been joined. it hands over two things:

  • the cluster ID, so user space knows which cluster we're talking about
  • a flag saying whether it's a new cluster or not, because context matters, always 💜

literally that's it. it's giving "small function, big responsibility" energy. it doesn't do the joining itself, it just announces the join to user space so everybody's on the same page. slay ✨

🌸 SEE ALSO 🌸

okay bestie, this is the part where the page basically goes "now go read literally everything else" 💀 and honestly? iconic behaviour. every single one of these is a real page you can pull up, so here's the whole squad, in order, no skips, no cap ✨

  • 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)
  • Neighbor Awareness Networking (NAN)(9) — whole section, our home turf 🦋

that's the whole friend group, bestie — every single one accounted for, nobody left on read 💖

...and we're not done yet, bestie 😭 the SEE ALSO list is long long, so buckle up — every single one of these is getting its moment, because we do not skip entries in this house 💅

the regulatory girlies said "we're all going on the list" and honestly? respect 🌸

okay next batch, no notes:

and now the combination/registration-adjacent section of the list, lowkey a whole vibe:

and then the nan squad showed up, because of course they did 💖

moving on before I get emotional:

the colour-change clique, they're all here and they're all matching 💅:

and the rest of the guest list, in order, no cap:

back to nan for round two because she simply had more to say 🙈:

final stretch, we made it 😭🎀:

and that's the whole list, every single one, we did it 🫶 this page came out of ./include/net and it's dated October 2026, so like — future queen behavior honestly 👑 go read the actual functions, stay curious, and drink some water, ily, bye 💖✨

📦 where this page comes from