enclosure_for_each_device(9)

🎀 enclosure_for_each_device(9) 🎀

okay so bestie, welcome to the Kernel API Manual. we’re looking at enclosure_for_each_device, and it’s literally giving “loop over every enclosure and call your function” energy. no details skipped, periodt 💅

---

✨ NAME ✨

enclosure_for_each_device — calls a function for each enclosure 🦋

---

🦋 SYNOPSIS 🦋

int enclosure_for_each_device (int (*fn)(struct enclosure_device *, void *) , void *data );

---

🍓 ARGUMENTS 🍓

• fn — the function to call 👑
• data — the data to pass to each call 🫶

---

🔥 DESCRIPTION 🔥

It loops over all the enclosures and calls the function. that’s the whole move, bestie ✨

⚠️ okay this part matters: this function uses a mutex which will be held across calls to fn, so it must have non atomic context. and fn may (although it should not 😭) sleep or otherwise cause the mutex to be held for indefinite periods. like… please do not make the mutex wait forever, i’m begging 💀

---

🌈 SEE ALSO 🌈

Kernel file ./drivers/misc/enclosure.c — and the whole friend group is here too:

• enclosure_find(9)
• enclosure_register(9)
• enclosure_unregister(9)
• enclosure_component_alloc(9)
• enclosure_component_register(9)
• enclosure_add_device(9)
• enclosure_remove_device(9)

---

okay bye bestie 🫶 source/version: ./drivers/misc, date: October 2026, manual: enclosure_for_each_device(9) — slay ✨💖