driver_probe_done(9)

💅 driver_probe_done — the Kernel API Manual ✨

okay so bestie, welcome to driver_probe_done(9), straight out of the Kernel API Manual. it's short, it's sweet, it's giving "little function, big feelings" 🎀

---

🌸 NAME 🌸

driver_probe_done — and honestly? the one-line description is literally empty. like, blank. nothing. the manpage authors said "she speaks for herself" 💀 so no cap, there's no tagline here, just vibes 🦋

---

✨ SYNOPSIS ✨

bool driver_probe_done (void );

that's it. that's the whole thing. returns a bool, takes nothing. iconic 🫶

---

🎀 ARGUMENTS 🎀

• void — no arguments, bestie. none. zero. it wants for nothing 🙈

---

🔥 DESCRIPTION 🔥

so what does it actually do? it determines if the probe sequence is finished or not. that's the whole job. is the probe sequence done? yes or no. main character energy, honestly 👑

but here's the tea ☕ — and this is straight from the manpage, i'm not making it up — the notes say it should somehow figure out how to use a semaphore, not an atomic variable...

bestie that "somehow" is doing SO much heavy lifting 😭 it's a known thing that this should be a semaphore and it just. isn't. yet. lowkey a TODO in the wild 🌈

---

🦋 SEE ALSO 🦋

• kernel file ./drivers/base/dd.c
• driver_deferred_probe_trigger(9)
• device_block_probing(9)
• device_unblock_probing(9)
• device_set_deferred_probe_reason(9)
• driver_deferred_probe_check_state(9)
• deferred_probe_initcall(9)
• device_is_bound(9)
• device_bind_driver(9)
• wait_for_device_probe(9)
• driver_probe_device(9)
• device_attach(9)
• device_driver_attach(9)
• driver_attach(9)
• device_release_driver(9)
• device_driver_detach(9)
• driver_detach(9)

like a whole friend group of probe-related functions. go read them too, they're all slaying in their own way 💜

---

and that's the page! sign-off time 🧚: this lil masterpiece lives under ./drivers/base and it's dated October 2026 — mark your calendars, screenshot it, send it to the group chat, periodt 💅✨