cfg80211_rem...nnel_expired(9)

📦 version 7.3.1, in nixpkgs unstable

✨ cfg80211_remain_on_channel_expired ✨

okay so bestie, welcome to the cfg80211_rem...nnel_expired(9) page — yeah the header's doing that truncated thing where the title got cut off, it's giving "my name is too long for the terminal" energy 😭 but it's fine, we know her, it's the Kernel API Manual and she's iconic. This is part 1 of 3 so stay with me, we're only getting started 💅

🌸 NAME 🌸

cfg80211_remain_on_channel_expired — literally the moment your remain_on_channel duration runs out. time's up, channel era over, periodt 💀

🦋 SYNOPSIS 🦋

void cfg80211_remain_on_channel_expired (struct wireless_dev *wdev , u64
       cookie , struct ieee80211_channel *chan , gfp_t gfp );

no cap, that's the whole signature. she takes four things and returns void — so like, she doesn't hand you anything back, she just does the thing and leaves ✨ main character energy honestly.

🎀 ARGUMENTS 🎀

  • wdev — the wireless device. your whole wireless-device struct, the star of the show, the one who's channel timer just expired 🫶
  • cookie — the request cookie 🍪 like yes literally that's what it's called. it's the cookie that came with the request, so everybody knows which request we're talking about. iykyk
  • chan — The current channel, and ngl the docs are very clear here: it comes from the remain_on_channel request, so it's not just some random channel she picked up off the street 💅
  • gfp — allocation flags 🌈 the classic gfp_t situation, you know her, you love her, she's in like every other kernel function

that's the setup bestie, the stage is set — and there is SO much more coming, so don't go anywhere 🌸

💅 SEE ALSO 💅

okay bestie, this is the part of the page where it name-drops literally every cousin in the wifi kernel family 💖. It's giving yearbook superlatives, and every single one of these is a real cross-reference you can go read. No cap, I'm keeping all of them, because you might actually need them.

…and that's where this chunk stops, bestie — the list literally keeps going in the next part, so hold that thought 💅

okay so. the cross-reference list on this page is absolutely unhinged — it's giving "the author hit tab-completion and never stopped". but bestie, every single one is here, in order, no skips. that's the whole assignment. 💅

and that's the whole list, bestie. sixty-four entries, zero shortcuts, my thumbs are sore 😭 notice how two of them are literally struct pages (struct cfg80211_ft_event_params(9) and struct cfg80211_mlo_reconf_done_data(9))? yeah, don't sleep on those, structs get manual pages too and they deserve their moment ✨

ngl the vibe of this page is "we documented one thing and then shouted out the entire subsystem". honestly? iconic. if you're looking for a specific function and it's not saved here, that's a skill issue on your grep, not on the page 🫶

go open whichever one you actually needed, read it properly, and don't just skim the SYNOPSIS like it's a text message preview. you got this 💖

🌸 quick sign-off before you close the tab: this page lives over at ./include/net, it's dated October 2026, and the header/footer line you'd normally see at the bottom is just the page name cfg80211_rem...nnel_expired(9) giving main character energy one last time. bye bestie, happy hacking 👑🎀

📦 where this page comes from