acpi_unregis...keup_handler(9)

💅 acpi_unregis...keup_handler(9) — like, the Kernel API Manual one, bestie

okay so first things first: yes, the title is literally truncated like that. acpi_unregis...keup_handler(9) — that's not me being lazy, that's just how the header/footer renders it, and honestly? iconic of it. The full name is in NAME below, don't stress 🫶

✨ NAME ✨

acpi_unregister_wakeup_handler — unregister a wakeup handler. That's it. That's the whole vibe. You're undoing a registration, bestie 💅

🌸 SYNOPSIS 🌸

void acpi_unregister_wakeup_handler (bool (*wakeup)(void *context) ,
void *context );

it returns void btw — so like, nothing comes back. she's not a giver, she's a doer ✨

🎀 ARGUMENTS 🎀

• wakeup — the wakeup-handler that you originally passed to acpi_register_wakeup_handler. same one, no swapsies 💖
• context — the context that you originally passed to acpi_register_wakeup_handler. also the same one. consistency is key, queen 👑

ngl the whole point here is that both of these need to match what you registered with. you're not inventing new stuff, you're just saying "hey, take that one back" 🦋

🔥 SEE ALSO 🔥

• kernel file ./drivers/acpi/wakeup.c — the source of truth, go read her 📖
• acpi_enable_wakeup_devices(9)
• acpi_disable_wakeup_devices(9)
• acpi_register_wakeup_handler(9) — the one that started it all 💫

and that's the whole page, bestie!! no cap, she's short and sweet 🌈 this came from the source tree at ./drivers/acpi, dated October 2026, and the page signs itself off as acpi_unregis...keup_handler(9) — yeah, still truncated, still slaying 💀✨ mwah 🫶