handle_eject_request(9)

💖 handle_eject_request(9) 💖

okay bestie, this page is straight out of the Kernel API Manual, and it's all about one little function that handles an undock request and checks for error conditions. lowkey iconic. 💅

---

🎀 NAME 🎀

handle_eject_request — handle an undock request checking for error conditions. yep, that's the whole assignment, no cap. ✨

---

✨ SYNOPSIS ✨

int handle_eject_request (struct dock_station *ds , u32 event );

---

🌸 ARGUMENTS 🌸

• ds — The dock station to undock. 🫶
• event — The ACPI event number associated with the undock request. 🔥

---

🦋 DESCRIPTION 🦋

First, it checks to make sure the dock device is still present. Then it undocks and hotremoves all the devices that may need removing. That's the flow, bestie — presence check ➡️ undock ➡️ hotremove the maybe-needs-removing devices. ✨

---

💜 SEE ALSO 💜

The kernel file is ./drivers/acpi/dock.c, and these are the related besties you should go peek at:

• add_dock_dependent_device(9)
• find_dock_dependent_device(9)
• is_dock_device(9)
• dock_present(9)
• hot_remove_dock_devices(9)
• hotplug_dock_devices(9)
• handle_dock(9)
• dock_in_progress(9)
• dock_notify(9)
• acpi_dock_add(9)

---

mwah 💋 that's the page! source/version: ./drivers/acpi · date: October 2026. byeee 🫶