__devm_mdiobus_register(9)

💅 __devm_mdiobus_register(9) — like, the whole vibe

okay so bestie, welcome to the Kernel API Manual ✨ this one is literally called __devm_mdiobus_register(9) and she is that girl — the resource-managed variant of mdiobus_register(). yes, the double-underscore is part of the name, don't @ me 🎀

---

✨ SYNOPSIS ✨

the whole thing in one breath, no cap:

int __devm_mdiobus_register (struct device *dev , struct mii_bus *bus ,
       struct module *owner );

like, three args, one int, iconic behavior honestly 🦋

---

🌸 ARGUMENTS 🌸

breaking it down one by one, because we don't gatekeep:

• dev — the device you're registering the mii_bus for. it's giving "who is this for" energy 💖
• bus — the actual MII bus structure you want to register. the main character, fr fr 👑
• owner — the owning module. gotta know whose module it is, iykyk 🌈

---

🫶 DESCRIPTION 🫶

okay so here's the whole deal, and it's literally one line: it returns 0 on success, and a negative error number on failure. that's it. that's the tea ☕

lowkey love a short description, no yapping, periodt 💅

ngl bestie, if you get a negative number back, that's the failure vibe check — don't ignore it, go read the error 😭

---

🦋 SEE ALSO 🦋

because we always cite our sources, bestie:

• the kernel file ./drivers/net/phy/mdio_devres.c 📁
• devm_mdiobus_alloc_size(9) — the alloc bestie 🧚
• __devm_of_mdiobus_register(9) — the device-tree-flavored sibling 💜

---

🎀 the cute sign-off 🎀

and that's the page, bestie! 🌸 this little beauty lives in ./drivers/net/phy, dated October 2026, and she answers to the name __devm_mdiobus_register(9) — so you already know where to find her again. mwah 💋✨🍓