regdom_intersect(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ¦‹ regdom_intersect(9) β€” the Kernel API Manual page, bestie edition ✨

okay so this is regdom_intersect from the Kernel API Manual and it's genuinely one of the most satisfying little functions ever β€” like, it takes two whole regulatory domains and finds the overlap?? main character energy fr πŸ’…


✨ NAME ✨

regdom_intersect β€” do the intersection between two regulatory domains


πŸŽ€ SYNOPSIS πŸŽ€

struct ieee80211_regdomain * regdom_intersect (const struct
       ieee80211_regdomain *rd1 , const struct ieee80211_regdomain *rd2 );

🌸 ARGUMENTS 🌸

  • rd1 β€” first regulatory domain. your girl number one 🫢
  • rd2 β€” second regulatory domain. the other one, also valid, also iconic πŸ’œ

⭐ DESCRIPTION ⭐

so like, use this function to get the intersection between two regulatory domains β€” literally the stuff they both agree on, no cap πŸ”₯

Once it's completed, we will mark the alpha2 for the rd as intersected, "98", because β€” and this is the important bit, bestie β€” no one single alpha2 can represent this regulatory domain. it's just too special for one country code πŸ˜­πŸ‘‘

Returns a pointer to the regulatory domain structure which will hold the resulting intersection of rules between rd1 and rd2. And don't even worry about the memory, because we will kzalloc this structure for you ✨🫢 (yes, zeroed out, yes, handed to you on a little platter, slay).


πŸ’– RETURN πŸ’–

the intersected regdomain 🌈


πŸ‘€ SEE ALSO πŸ‘€

all of these are lowkey part of the same wireless reg circus and you should absolutely go read them, iykyk πŸ’€πŸ’–


heads up: the "98" alpha2 marker is not a real country code, it's literally just us flagging "this domain is an intersection" β€” do not go looking for country 98, she does not exist πŸ™ˆ

and that's the whole page!! brought to you from ./net/wireless, dated October 2026, in the Kernel API Manual β€” regdom_intersect(9) out here being a whole legend. mwah, periodt πŸ’‹πŸŽ€

πŸ“¦ where this page comes from