cfg80211_co...rt_tx_status(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ cfg80211_control_port_tx_status β€” Kernel API Manual ✨

okay bestie, welcome to the Kernel API Manual πŸ’– this one is called cfg80211_control_port_tx_status and it's literally all about telling the kernel how a control port frame's transmission went. no cap, that's the whole vibe.


🌸 NAME 🌸

cfg80211_control_port_tx_status β€” the notification of TX status for control port frames πŸŽ€

like, "hey bestie, here's what happened when we tried to send this frame" β€” that's the whole job.


πŸ¦‹ SYNOPSIS πŸ¦‹

void cfg80211_control_port_tx_status (struct wireless_dev *wdev , u64
cookie , const u8 *buf , size_t len , bool ack , gfp_t gfp );

she takes six arguments and returns void β€” no return value, no drama, just vibes and a status report ✨


πŸ’… ARGUMENTS πŸ’…

  • wdev β€” the wireless device receiving the frame 🫢 like, which device are we talking about here, bestie?
  • cookie β€” the cookie returned by cfg80211_ops::tx_control_port πŸͺ yep, that exact one β€” it's how we match the status back up with the original request.
  • buf β€” the data frame (header + body) πŸ“¦ header and body, both, together, the whole package.
  • len β€” the length of the frame data πŸ“ how many bytes are in that buf, fr fr.
  • ack β€” whether the frame was acknowledged βœ… a bool, so it's a straight yes-or-no situation.
  • gfp β€” the context flags 🌈 you know the drill, the allocation context flags.

πŸ”₯ DESCRIPTION πŸ”₯

so here's the tea β˜• β€” this function gets called whenever a control port frame was requested to be transmitted with cfg80211_ops::tx_control_port, and its whole main character job is to report the TX status of that transmission attempt πŸ’«

basically: you asked for a control port frame to go out, now you come back and tell everyone how it went. iconic behavior, honestly πŸ‘‘


more coming, bestie β€” this was just part 1 🧚

🌸 SEE ALSO 🌸

okay bestie, brace yourself πŸ’€ because this is the part where the page just dumps the entire friend group. every struct, every enum, every function that lives anywhere near this one in ./include/net/cfg80211.h. it's giving "tag yourself i'm struct cfg80211_bss". do NOT panic β€” it's just the guest list, and you don't have to meet all of them tonight. πŸ’…


okay now we're entering actions and configuration territory and it is long. highkey the main character section of the whole file πŸ”₯


πŸ¦‹ the scanning + BSS list handling era πŸ¦‹

  • Scanning and BSS list handling(9) is the section header vibe, then it's structs for days: 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)
  • BSS getters and the connect-request family: 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)
  • connect params!! plus wowlan everything (there are SO many wowlan structs and honestly? respect πŸ’œ): 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)
  • rekeying, ft, mgmt tx, and the qos/dscp cuties: 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) corner 🧚

  • Neighbor Awareness Networking (NAN)(9) β€” yes it gets its own little section and yes it's adorable: 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)
  • back to the main lineup: struct cfg80211_pmk_conf(9), struct cfg80211_external_auth_params(9), struct cfg80211_ftm_responder_stats(9), struct cfg80211_pmsr_ftm_result(9), struct cfg80211_pmsr_result(9), struct cfg80211_pmsr_ftm_request_peer(9), struct cfg80211_pmsr_request_peer(9), struct cfg80211_pmsr_request(9), struct cfg80211_update_owe_info(9), struct mgmt_frame_regs(9)

πŸ‘‘ wiphy o'clock πŸ‘‘


🌈 Utility functions 🌈


⭐ Data path helpers ⭐


πŸŽ€ Regulatory enforcement infrastructure πŸŽ€


πŸ’– scan done + BSS notification zone πŸ’–


and that's the guest list, bestie β€” take a breath, hydrate, stretch your scrolling finger πŸ“ the page keeps going though, so don't wander off πŸ‘€

...and it keeps going 😭 bestie this page has SO many friends, she's the most popular girl in the kernel and honestly? deserved. okay, part three is literally just the rest of the SEE ALSO clique, so let's speed-run the roll call πŸ’…


okay halfway through the tag list, stay with me, we're doing great 🫢 look at all these informational-elements girlies and registration besties living their truth:


the NAN girlies and the colour-change girlies are literally carrying this section, no cap πŸ’€βœ¨


bestie that's the whole list, every single one of them, not one skipped β€” go click through them whenever you're ready, they're all right there in section 9 πŸ’–

aaaand that's a wrap on the page, icon behaviour honestly πŸ‘‘ fr fr you just read the entire cross-reference friend group. if you got this far, you're lowkey a wireless-networking main character now.

✨ the end ✨ β€” this page lives in ./include/net, dated October 2026, and it's filed under cfg80211_co...rt_tx_status(9) (yes the title is still abbreviated like that, she's mysterious, we love her for it πŸ’…). mwah, go touch grass β€” or better, go read the man pages πŸŒΈπŸ¦‹

πŸ“¦ where this page comes from