ieee80211_e..._delay_in_us(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ieee80211_e..._delay_in_us(9) β€” like, the Kernel API Manual page, bestie πŸŽ€

okay so welcome to the Kernel API Manual, specifically the page for ieee80211_emlmr_pad_delay_in_us, which ngl has a name so long the header had to abbreviate it and honestly? relatable. it's giving "my function name is my whole personality" energy and we love that for it. ✨


🌸 NAME 🌸

ieee80211_emlmr_pad_delay_in_us β€” fetches the EMLMR Padding delay in microseconds. that's it. that's the whole job. she's a getter, she's iconic, she's employed. πŸ’…


✨ SYNOPSIS ✨

u32 ieee80211_emlmr_pad_delay_in_us(u16 eml_cap);

so you hand her a u16 and she gives you back a u32, and the vibe check passes. simple as. 🫢


πŸ¦‹ ARGUMENTS πŸ¦‹

  • eml_cap β€” the EML capabilities field value, straight up from the common info field of the Multi-link element. like that's the whole thing you pass in, no cap. it's the source of truth for this entire function and she does not ask questions. πŸ“

πŸ’– RETURN πŸ’–

the EMLMR Padding delay (in microseconds), decoded from the EML Capabilities field. yes bestie, it comes back as a u32 and it is a time, in microseconds, and it is padding, and it is EMLMR. every word in that sentence is load-bearing. 😭πŸ”₯


🌈 SEE ALSO 🌈

okay buckle up because this list is LONG and honestly kind of a serve. the kernel file lives at ./include/linux/ieee80211-eht.h and here's everyone she's adjacent to in the group chat:

no because why is that list longer than my screen 😭 but every single one of them is here, exactly as written, because we do NOT abbreviate the homies. πŸ‘‘


ok that's the whole page, bestie. nothing hidden, nothing skipped, all facts intact. slay. πŸ’œ

and finally, the boring-but-important bits: this page comes from the source path ./include/linux and it's dated October 2026, so if you're reading this from the future β€” hey, hope the kernel is thriving 🧚✨ mwah, bye! πŸŽ€

πŸ“¦ where this page comes from