ath_reg_apply_ir_flags(9)

💅 ath_reg_apply_ir_flags(9) 💅

okay so bestie, welcome to the Kernel API Manual ✨ — yes that's the manual name, and yes it's the whole vibe. today we're talking about ath_reg_apply_ir_flags, which tbh doesn't even have a one-liner in its NAME section, so like… it's mysterious, it's enigmatic, it's giving main character energy 🎀. we move.

---

🌸 NAME 🌸

ath_reg_apply_ir_flags — literally that's it, that's the name, no blurb, no nothing 💀. iconic of it honestly.

---

✨ SYNOPSIS ✨

void ath_reg_apply_ir_flags (struct wiphy *wiphy , struct ath_regulatory
*reg , enum nl80211_reg_initiator initiator );

it returns void, so no sneaky return values to worry about 🫶. copy those types EXACTLY, no cap.

---

🎀 ARGUMENTS 🎀

• wiphy — the wiphy you're working with 💖 like, this is the stuff you pass in, bestie.
• reg — the regulatory structure, and the glow-up here is that it's used for country selection 🌍✨.
• initiator — the regulatory hint initiator 🦋 that's the thing that kicked this whole thing off.

---

🔥 DESCRIPTION 🔥

okay so here's the tea ☕. If no country IE has been received, then always enable passive scan and no-ibss on these channels 💅. and ngl, this is only done for specific regulatory SKUs — so don't go thinking it's a universal thing, because it is not, periodt 🙈.

then, if a country IE has been received, you gotta check its rule for this channel first before enabling active scan 👑. because the passive scan would have already been enforced by the initial processing of our custom regulatory domain — so like, respect the order of operations, bestie 🧚.

fr fr though: check the rule first. don't skip ahead. that's the whole point 😤.

---

🦋 SEE ALSO 🦋

• Kernel file ./drivers/net/wireless/ath/regd.c — go read it, iykyk 📖✨

---

and that's the page, bestie 💜! this slayed its way out of ./drivers/net/wireless/ath back in October 2026, and the manual itself is ath_reg_apply_ir_flags(9) — go off, king 👑. mwah 💋🌸