wiphy_dev(9)

📦 version 7.3.1, in nixpkgs unstable

🌸 wiphy_dev(9) — Kernel API Manual 🌸

okay bestie, welcome to the wiphy_dev page, straight out of the Kernel API Manual. this one is short and sweet — it's literally just "gimme the device pointer for this wiphy" and that's it. no cap. ✨

💖 NAME 💖

wiphy_dev — get wiphy dev pointer

like, that's the whole job. get the dev pointer. for the wiphy. iconic behaviour honestly 💅

🦋 SYNOPSIS 🦋

struct device * wiphy_dev (struct wiphy *wiphy );

so you call it with a struct wiphy *, and it hands you back a struct device *. that's the shape of it, fr fr. copy it exactly if you're typing it out — don't be out here changing signatures, that's giving chaos 🫶

🎀 ARGUMENTS 🎀

  • wiphy — the wiphy whose device struct you wanna look up. that's it. that's the one thing you pass in, and it's the wiphy you're asking about 👑

⭐ RETURN ⭐

the dev of wiphy. yes, that's literally what the manpage says and we're keeping it, because facts are facts 💯

so: you give it a wiphy, you get back its dev. simple as. the way that this function is just doing exactly one thing and doing it well — main character energy, lowkey 🌈

part 1 done, more coming, don't go anywhere bestie 💜

✨ SEE ALSO ✨

okay bestie, this SEE ALSO list is literally the group chat of cfg80211 — every ref is invited, nobody gets left on read 💅✨ Here’s the full roster, zero skips:

okay continuing the list, bestie — we're still deep in the SEE ALSO rabbit hole and honestly? it's a whole ecosystem down here 💜 every single one of these has its own page, so go be nosy:

like, that's sixty-four pages. sixty-four!! no cap, the wireless stack is huge and it ate. go read them all if you want to be built different 💖

that's the whole page bestie, we did it 🫶 this one lives over in ./include/net, and it's dated October 2026 — so yeah, future-dated manpage, very main character of her. mwah, go write some slayful wireless code 💅✨

📦 where this page comes from