cfg80211_col...arted_notify(9)

📦 version 7.3.1, in nixpkgs unstable

💅 cfg80211_color_change_started_notify 💅

okay so bestie, welcome to the Kernel API Manual ✨ — this is a (9) page, which is kernel-doc speak for "yes queen, this is a function". Buckle up, we're talking about telling userspace that a color change just kicked off 🎨🦋

🌸 NAME 🌸

cfg80211_color_change_started_notify — literally the function that notifies people that the color change has started. that's it, that's the vibe 🎀

✨ SYNOPSIS ✨

int cfg80211_color_change_started_notify(struct net_device *dev, u8 count, u8 link_id);

so it returns an int (as one does 💅), and it takes three lil arguments. and yes, the header up top shortens it to cfg80211_col...arted_notify(9) because terminal widths are haters 😭 — the real name is the whole thing, no cap.

🫶 ARGUMENTS 🫶

  • dev — the device on which the color is switched 🎨 this is your struct net_device *, the main character of the operation, the one actually getting its color changed.
  • count — the number of TBTTs until the color change happens ⏳ like, how many TBTTs are we waiting, bestie? that's a u8, keep it cute and small.
  • link_id — a valid link_id in case of MLO, or 0 for non-MLO 🌈 two whole moods. MLO girlies pass a real link id; everyone else passes 0 and moves on.

🔥 DESCRIPTION 🔥

Inform the userspace about the color change that has started. 📣✨

that's the whole assignment. userspace gets the heads-up that the color change is underway — not finished, started. it's giving "hey bestie, just so you know, it's happening" energy 💖

⭐ RETURN ⭐

  • 0 on success 🎉 slay, it worked, we love to see it.
  • Non-zero on error 💀 which means something went sideways and you should probably go look at that.
part 1 of 3, bestie — don't go anywhere, there's more coming 👑💜

👀 SEE ALSO 👀

okay bestie, so this page is like the group chat of kernel symbols and it has so many friends. FR fr, this is the whole "you may also be obsessed with" list, so grab a snack 🍓 — everything below is exactly the cross-reference gang, one per line, no cap:

✨ Actions and configuration ✨</p>

this whole next block is the main character energy bit — channels, beacons, stations, all of it 💅

🦋 Scanning and BSS list handling 🦋

the "who's out there" era 🔍 scanning, matching, connecting, and also wowlan because apparently we nap sometimes 😴

  • 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 era + everything wiphy 🧚

🌸 Utility functions 🌸

little helper besties that do one job and do it cute ✨

🍓 Data path helpers 🍓

this is where the packets actually get handled, and honestly it ate 💅

👑 Regulatory enforcement infrastructure 👑

the "please don't transmit there, bestie" department 📻 literally the law

the internal ones 🙈

💖 notifications, events, and all the rest 💖

and now the big stretch — all the done/failed/notify/found functions that keep everyone in the loop 🫶

🛰️ RFkill integration 🛰️

the airplane-mode girlies ✈️

🎀 Vendor commands 🎀

vendor-specific slay, iykyk 💅

🧪 Test mode 🧪

for the experimenting girlies — the testmode era 🔥

okay and then the rest of the gang rolls in, no break in the vibe 💜:

and yeah, the list literally keeps going — catch you in the next part bestie 😭💖

…and the cross-refs keep going, bestie, because this page is thorough. Here's the rest of the family — no skipping, every single one, in order 💅

okay notice how the ieee80211_*_to_* girlies are literally just converting one thing into another? they're the translators of the group chat 🌈 and yes we love a consistent naming scheme.

the stop_* and shutdown_* trio said "we're the ones who end things" and honestly? main character energy 🫶 (also peep struct cfg80211_ft_event_params(9) — a whole struct got a page, we stan).

wiphy_ext_feature_set(9) and wiphy_ext_feature_isset(9) are giving setter/getter sibling duo, and the nan cluster is thriving ✨ also cfg80211_assoc_comeback(9) — the name alone, I can't 😭

the _notify girlies are all over this list, and the debugfs read/write pair said "we come as a set" 💀 and there's the whole s1g_get_* squad at the end — start freq, end freq, primary sibling, all present and accounted for 👑

bestie reminder: that's the whole list, nothing dropped, nothing merged, nothing "cleaned up". if you need a symbol, it's up there fr fr 🦋

and that's a wrap on <rainbow>cfg80211_col...arted_notify(9)</rainbow> 🎀 this beauty lives over in ./include/net, stamped October 2026, and yes it's still rocking that truncated-looking title like it's a mystery novel. go forth and beacon responsibly, icon 💖✨🌸

📦 where this page comes from