wiphy_ext_feature_isset(9)

📦 version 7.3.1, in nixpkgs unstable

🌸 wiphy_ext_feature_isset (9) — Kernel API Manual 🌸

okay so bestie, welcome to the wiphy_ext_feature_isset page — yes that's a whole mouthful, i know, but it's so much shorter than it looks, i promise. this is the Kernel API Manual page for it, and we're gonna get through it together. grab a snack. 🍓

✨ NAME ✨

wiphy_ext_feature_isset — the one where you check the extended feature flag 💅

literally that's it. that's the whole job. check a flag. icon behavior, no notes.

🦋 SYNOPSIS 🦋

bool wiphy_ext_feature_isset (struct wiphy *wiphy , enum
       nl80211_ext_feature_index ftidx );

so it takes a struct wiphy * and an enum nl80211_ext_feature_index, and hands you back a bool. that's the vibe check in one line, fr fr.

🎀 ARGUMENTS 🎀

  • wiphy — the wiphy to modify. 👑 that's your main character struct right there.
  • ftidx — extended feature bit index. 🧚 this is the little number that says which bit we're peeking at.

💜 DESCRIPTION 💜

okay so here's the tea: the extended features are flagged in multiple bytes — like, not just one byte, a whole handful of them. and if you wanna see the receipts, go look at struct wiphy.ext_features. 😭 that's where they all live.

so your boi wiphy_ext_feature_isset is just going "hey, is this extended feature flag set or not?" and letting you know. simple as. no cap.

⭐ RETURN ⭐

  • true if the extended feature flag is set ✨
  • false otherwise 💀

periodt. that's the return contract, and it's giving exactly what it needs to give. 🫶

(part 1 done — more parts coming, don't go anywhere bestie 💖)

💖 SEE ALSO 💖

okay bestie, this is the cross-reference motherload — every single one of these is linked from the same kernel file, and yes, the list is giving phone book energy. No skips, no cap:

ok bestie, buckle up, because this cross-reference list is long long — but you asked for every single one and I would never do you dirty by trimming. These are all (9) pages, aka kernel-doc pages for internal functions, so hit them up whenever you need the full tea on any of them 💅

lowkey a whole friend group up in here 😭 like yes there are sixty-three of them and no I did not skip a single one, because the rule is: the vibe changes, the facts do not. Take my hand, click through, slay 🫶

and that's a wrap on the whole page, bestie!! 🎀✨ you made it to the end of the cross-references, which honestly deserves a little certificate 🏆 this one's filed under ./include/net in the October 2026 edition of the docs, so if anything looks different in your checkout, that's your timestamp to blame 💜 go forth and isset those extended features, periodt 🌸

📦 where this page comes from