STRUCT CFG80211_SAR_SPECS(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

struct cfg80211_sar_specs β€” the sar limit specs bestie, literally the whole vibe of SAR limits in one struct ✨

This is page struct cfg80211_sar_specs(9) from the Kernel API Manual, and we're doing this in three parts, so buckle up πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

okay so here's the actual struct, exactly as it lives, no cap:

struct cfg80211_sar_specs {
    enum nl80211_sar_type type;
    u32 num_sub_specs;
    struct cfg80211_sar_sub_specs sub_specs[];
};

look at her. iconic. she's got a type, she's got a count, she's got a flexible array member at the end (the [] is doing main character energy fr fr) πŸ‘‘


🌸 Members 🌸

  • type β€” this one gets set with power in 0.25dbm, or with other types. that's the whole assignment πŸ’…
  • num_sub_specs β€” the number of sar sub specs. yes bestie, it's counting them. it's giving inventory management 🧚
  • sub_specs β€” the memory that holds the sar sub specs. like, the actual storage spot. the sub_specs[] flexible array of the family 🫢

and that's the struct itself β€” the fields, the types, the exact names, all of it. more staying tuned energy coming in the next part ⭐

✨ SEE ALSO ✨

okay so this is the cross-reference yearbook πŸ“š β€” every single (9) from the original is invited to the group chat, zero skips, zero β€œetc.” energy. bestie, this is the whole squad:

…and the list keeps going, bestie, because the wireless stack does not know how to stop. Finish line's right here 🏁


And that's the whole squad 🫢 S1G got its moment, NAN showed up four separate times like it's the main character, MLO reconf is thriving, and yes β€” color change has three whole notifications because apparently one was simply not enough πŸ’…

That's the end of the page, so let me hand you the receipts: this one lives in ./include/net, it's dated October 2026, and the page you just read is struct cfg80211_sar_specs(9). Slay, go read some kernel source, ily, bye πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from