ssam_device_..._hot_removed(9)

🌸 NAME 🌸

okay bestie, welcome to ssam_device_..._hot_removed(9) from the Kernel API Manual — this is the page for ssam_device_mark_hot_removed, and it does exactly what it says on the tin: mark the given device as hot-removed. periodt 💅

---

✨ SYNOPSIS ✨

the whole signature is giving:

void ssam_device_mark_hot_removed (struct ssam_device *sdev );

---

🫶 ARGUMENTS 🫶

• sdev — the device to mark as hot-removed. that's the one, bestie 🎀

---

💖 DESCRIPTION 💖

okay so this function marks the device as having been hot-removed. it's literally signaling drivers that are using the device that communication with the device should be avoided — and fr fr, that communication may lead to timeouts. so yeah, drivers get the memo: maybe don't talk to it 💀

not me emphasizing this: communication with the device should be avoided and may lead to timeouts. that's the whole vibe check.

---

🦋 SEE ALSO 🦋

go look at these besties too, no skips:

• Kernel file ./include/linux/surface_aggregator/device.h
• enum ssam_device_domain(9)
• enum ssam_virtual_tc(9)
• struct ssam_device_uid(9)
• SSAM_DEVICE(9)
• SSAM_VDEV(9)
• SSAM_SDEV(9)
• struct ssam_device(9)
• struct ssam_device_driver(9)
• is_ssam_device(9)
• to_ssam_device(9)
• to_ssam_device_driver(9)
• ssam_device_is_hot_removed(9)
• ssam_device_get(9)
• ssam_device_put(9)
• ssam_device_get_drvdata(9)
• ssam_device_set_drvdata(9)
• ssam_device_driver_register(9)
• module_ssam_device_driver(9)
• ssam_register_clients(9)
• ssam_device_register_clients(9)
• SSAM_DEFINE_SYNC_REQUEST_CL_N(9)
• SSAM_DEFINE_SYNC_REQUEST_CL_W(9)
• SSAM_DEFINE_SYNC_REQUEST_CL_R(9)
• SSAM_DEFINE_SYNC_REQUEST_CL_WR(9)
• ssam_device_notifier_register(9)
• ssam_device_notifier_unregister(9)

---

and that's the page, bestie 🫶 this footer vibe is brought to you by source/version ./include/linux/surface_aggreg..., dated October 2026, for ssam_device_..._hot_removed(9) — mwah 💋✨