ENUM REG_REQUEST_TREATMENT(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– enum reg_request_treatment(9) β€” the Kernel API Manual glow-up πŸŽ€

okay so bestie, picture this: you're deep in the kernel, the wireless regulatory stuff is happening, and somebody hands you a request. and you're like… "what do i even do with this?" 😭 that's literally this enum. it's the vibe check for regulatory requests β€” four little constants that tell the code whether to keep going, yeet it, merge it, or just chill because it's already done. welcome to the group chat. πŸ¦‹

it lives in the Kernel API Manual, and it's giving main-character energy for ./net/wireless. periodt. ✨


✨ SYNOPSIS ✨

enum reg_request_treatment {
    REG_REQ_OK ,
    REG_REQ_IGNORE ,
    REG_REQ_INTERSECT ,
    REG_REQ_ALREADY_SET

};

like, that's it. that's the whole roster. four icons and they all mean something different. πŸ‘‘


🌸 CONSTANTS 🌸

  • REG_REQ_OK β€” bestie said yes πŸ’… continue processing the regulatory request. we're so back.
  • REG_REQ_IGNORE β€” nope, not today. πŸ™ˆ just ignore the regulatory request entirely. blocked. deleted. moving on.
  • REG_REQ_INTERSECT β€” ooh she's doing math 🧚 the regulatory domain that results from this request should be intersected with the current one. two domains, one overlap, no cap.
  • REG_REQ_ALREADY_SET β€” girl it's already done πŸ’€ this regulatory request will not change the current regulatory settings, and no further processing is required. we can all go home. 🫢

⭐ SEE ALSO ⭐

the lore continues, iykyk:


πŸ’– friendly reminder: these constants aren't just cute names, they're the actual control flow. treat REG_REQ_ALREADY_SET with the respect it deserves β€” it's telling you to stop working. 😌

and that's the whole page, bestie! 🌈 brought to you from ./net/wireless, dated October 2026, filed under enum reg_request_treatment(9) β€” slay, go touch some regulatory domains. πŸ’œπŸŽ€πŸ”₯

πŸ“¦ where this page comes from