wiphy_delayed_work_cancel(9)

📦 version 7.3.1, in nixpkgs unstable

💅 wiphy_delayed_work_cancel(9)

okay bestie, so this is a page straight out of the Kernel API Manual — section 9, kernel developer land, no cap. Buckle up 🎀

✨ NAME ✨

wiphy_delayed_work_cancel — literally just cancels delayed work you queued up earlier. that's the whole vibe 🦋

🌸 SYNOPSIS 🌸

void wiphy_delayed_work_cancel (struct wiphy *wiphy , struct
wiphy_delayed_work *dwork );

it returns void, meaning it hands you nothing back — no little treat, no return code, nothing. it just does the thing 💅

🎀 ARGUMENTS 🎀

  • wiphy — the wiphy in question. and honestly? it's only here for debug purposes. it's giving emotional support parameter, and we respect it for that 🫶
  • dwork — the delayed work you want to cancel. the main character of this whole function, fr fr 👑

💖 DESCRIPTION 💖

so here's the tea: this cancels the work without waiting for it. like, it does not sit around tapping its foot until the work finishes. it's out the door immediately, no looking back 😭

⚠️ careful though, bestie — this assumes you're calling it while holding the wiphy mutex, the one you got by calling wiphy_lock. not holding it? that's a vibe check fail. lock first, then cancel. periodt 🔥

more coming in the next parts, don't go anywhere 🧚✨

🌈 SEE ALSO 🌈

ok bestie so this function does not live in a vacuum, and the SEE ALSO list is genuinely an entire tour of the wireless stack 💀 like the kernel said "here's your cross-reference list" and then handed us a whole friend group. Everything down there is a (9) page (kernel-doc man section), and the source file for basically the entire party is ./include/net/cfg80211.h.

I'm not skipping any of them. All of them. In order. Grab a snack 🍓.

🫶 starting with the source file itself

The page literally opens by pointing at the kernel file it was generated from, then rolls into the intro and the band / channel / rate plumbing:

note the _ieee80211_set_sband_iftype_data(9) with the leading underscore — that one is a different page from the non-underscore one, so don't come for me, they're both here fr fr 💅

🎀 actions and configuration era

Here's where we get into the doing-stuff side of the house:

that's a lot of struct bestie, I know 😭 but they're all real pages, I promise.

🔍 scanning and BSS list handling

  • 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 girl summer

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

👑 the wiphy struct / ops section (aka literally our girl's neighbourhood)

this is the chunk where our function's actual relatives live, so like… pay attention 🫶:

see? wiphy_delayed_work_queue(9), wiphy_delayed_work_flush(9) and wiphy_delayed_work_pending(9) are all right there, in a little row, like a group chat 💜

🧚 utility functions & data path helpers

⭐ regulatory + all the notification callbacks

...and we're still going, bestie 😭 the SEE ALSO list here is long long, like it ate and left no crumbs. Every single one of these is part of the same friend group, so here's the whole roster, nobody gets left behind 💅

the beacon / reg crew 🎀

channel switch & chandef girlies 🦋

assorted cfg80211_ icons ✨

the IE-splitting squad 🌸

reporting & stopping & interface things 🫶

feature flags, lowkey iconic ⭐

the NAN girlies (there are so many of them, periodt) 💖

auth, pmsr & misc main-character energy 👑

the whole colour-change saga 🌈

6 GHz, MLO & the scheduler besties 🔥

the rest of the NAN extended lore 💀

debugfs + S1G + one (1) incumbent signal 🙈

okay that's genuinely everyone, all 64 of them, no cap 🍓 if you were looking for one specific function in here, bestie it is in there, go get it — and if you need the rest of the wiphy_delayed_work_cancel(9) tea, it's all up above in the earlier sections. iykyk 💜

ngl, this list is giving "the whole contact list got dumped in the group chat" vibes, but it's fr fr every single cross-reference from the original page, untouched and exactly as written 🎀

that's a wrap, bestie!! 🧚 this page lives in ./include/net, it's dated October 2026, and it's the man page for wiphy_delayed_work_cancel(9) — go forth and slay your kernel work 💅✨

📦 where this page comes from