bus_find_next_device(9)

💅 bus_find_next_device (kernel API manual, bestie!!)

okay so this is a page from the Kernel API Manual — yes, the real one — and today's main character is bus_find_next_device. it's giving "where's the next one" energy and honestly? iconic.

---

✨ NAME ✨

bus_find_next_device — find the next device after a given device in a given bus. literally that's it, that's the whole vibe: you hand it a device, it goes "okay but who's next" 🦋

---

🌸 SYNOPSIS 🌸

struct device * bus_find_next_device (const struct bus_type *bus ,
struct device *cur );

it returns a struct device *, no cap. two things go in, one device pointer comes out 👑

---

🎀 ARGUMENTS 🎀

• bus — the bus type. the bus we're snooping around in, bestie 🚌
• cur — device to begin the search with. the starting point, the "before" picture, the place you're picking up from 🫶

---

🔥 SEE ALSO 🔥

• Kernel file ./include/linux/device/bus.h — and specifically struct bus_type(9), which is like the blueprint for the whole bus situation
• bus_find_device_by_name(9) — finding a device by its name
• bus_find_device_by_of_node(9) — finding one by device-tree node
• bus_find_device_by_fwnode(9) — finding one by firmware node
• bus_find_device_by_devt(9) — finding one by dev_t
• bus_find_device_by_acpi_dev(9) — finding one by ACPI device
• enum bus_notifier_event(9) — for when you wanna know what's happening on the bus 👀

go read those too, iykwim 💜

---

ngl this one's short and sweet — no options, no exit statuses, no traps. just a device pointer and good vibes ✨

---

okay bye bestie, this page lived at ./include/linux/device, it's stamped October 2026, and the manual's name is bus_find_next_device(9) — remember it fondly, slay 💅🎀