ieee80211_mle_get_eml_cap(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ieee80211_mle_get_eml_cap(9) β€” the Kernel API Manual page, bestie edition

okay so this one's from the Kernel API Manual and it's literally so straightforward, we're just grabbing one little field out of a multi-link element and running away with it. no cap, it's giving "one-line helper, main character energy." πŸŽ€


✨ NAME ✨

ieee80211_mle_get_eml_cap β€” returns the EML capability πŸ¦‹

✨ SYNOPSIS ✨

u16 ieee80211_mle_get_eml_cap (const u8 *data );

✨ ARGUMENTS ✨

  • data β€” pointer to the multi-link element. that's it. that's the whole argument. she's just a const u8 * pointing at your multi-link element and honestly she's slaying πŸ’…

✨ RETURN ✨

it hands you back the EML capability field value from the multi-link element. and if it's not present? you get 0, bestie. empty hands, zero drama πŸ™ˆ

✨ DESCRIPTION ✨

so here's the vibe check: the element is assumed to be of the correct type β€” that's BASIC β€” and big enough. but "assumed" is doing so much heavy lifting here, because this function does not check any of that for you 😭

⚠️ literally must be checked using ieee80211_mle_type_ok. do not skip this step. this is not a drill. she trusts you, and you should not betray her πŸ’€

✨ SEE ALSO ✨

like, the whole friend group showed up to the see-also section. iconic πŸ‘‘


and that's the whole page, bestie πŸ’– this one lives in ./include/linux, dated October 2026, and it goes by the name ieee80211_mle_get_eml_cap(9) β€” go check that type first, ily, bye 🫢🌸

πŸ“¦ where this page comes from