rfkill_unregister(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– rfkill_unregister(9) πŸ’–

okay so bestie, this is a page straight out of the Kernel API Manual β€” yes, the kernel, we're being fancy today πŸ‘‘


✨ NAME ✨

rfkill_unregister β€” the function that unregisters a rfkill structure. that's it, that's the whole vibe. bye-bye rfkill πŸ‘‹


🌸 SYNOPSIS 🌸

void rfkill_unregister (struct rfkill *rfkill );

it's void, so it gives nothing back β€” it just does the thing and leaves. main character energy tbh πŸ’…


πŸŽ€ ARGUMENTS πŸŽ€

  • rfkill β€” the rfkill structure that's getting unregistered. that's the one being sent off 🫢

πŸ¦‹ DESCRIPTION πŸ¦‹

so here's the tea β˜• β€” your network driver should call this function during device teardown, and its whole job is to destroy the rfkill structure. like, clean up your mess, bestie.

and listen, this part is important: until it returns, the driver needs to be able to service method calls. not after, not "whenever it feels like it" β€” until it returns. so don't go tearing down the thing that answers the phone before this function is done doing its little goodbye dance, okay? ngl this is the kind of detail that lowkey matters 🫑

πŸ’€ fr fr: keep servicing those method calls until rfkill_unregister comes back. no cap.

🌈 SEE ALSO 🌈

the whole squad, gathered for you πŸŽ€:

like an entire friend group of rfkill functions, and honestly? obsessed πŸ’œ


okay that's the page!! it lives in ./include/linux, it's dated October 2026, and it's part of the Kernel API Manual β€” slay, go unregister something responsibly βœ¨πŸ§šπŸ’–

πŸ“¦ where this page comes from