rfkill_epo(9)

✨ rfkill_epo(9) ✨

okay so real talk, this one's from the kernel API manual, section 9, and it's lowkey the nuclear option 💅

---

💖 NAME 💖

rfkill_epo — emergency power off all transmitters 🔥

---

🌸 SYNOPSIS 🌸

void rfkill_epo (void );

---

🎀 ARGUMENTS 🎀

• void — no arguments, bestie. none. zero. it takes literally nothing 🫶

---

🦋 DESCRIPTION 🦋

okay so picture this: this function kicks every single non-suspended rfkill device straight into RFKILL_STATE_SOFT_BLOCKED 😤 like it's on a mission and nothing is standing in its way — it ignores everything in its path except rfkill_global_mutex and rfkill->mutex. that's it. those two are the only things it respects. everything else? not even acknowledged 💀

and the icon that it is? it remembers ✨ the global state from before the EPO gets saved, so you can bring it back later with rfkill_restore_states. no cap, it's giving responsible queen energy 👑

ngl "emergency power off" means emergency power off — this is the dramatic main character move of the rfkill world, so treat it like one 🙈

---

🌈 SEE ALSO 🌈

• the kernel file ./net/rfkill/core.c
• rfkill_set_block(9)
• __rfkill_switch_all(9)
• rfkill_switch_all(9)
• rfkill_restore_states(9)
• rfkill_remove_epo_lock(9)
• rfkill_is_epo_lock_active(9)
• rfkill_get_global_sw_state(9)

go read the whole friend group, iykyk 🧚

---

and that's the page, bestie 💜 it lives in ./net/rfkill and it's dated October 2026, with rfkill_epo(9) stamped on it like a little signature 🎀 slay, go block those transmitters responsibly 🦋✨