realtek_mdio_remove(9)

📦 version 7.3.1, in nixpkgs unstable

💅 realtek_mdio_remove(9) — the kernel API manual, but make it make sense ✨

okay so bestie, you found realtek_mdio_remove in the kernel API manual and you're like "what does this even do" — don't worry, I got you 🫶 this is the page for taking a Realtek switch (the MDIO-connected kind) and yeeting it out of existence, gracefully, the way a main character exits a party 💅

🌸 NAME 🌸

realtek_mdio_remove — remove the driver of an MDIO-connected switch, no cap 🔥

🎀 SYNOPSIS 🎀

void realtek_mdio_remove (struct mdio_device *mdiodev );

that's it. that's the whole signature. mdiodev is a struct mdio_device * and the function returns void, so nothing comes back out. iconic, honestly ✨

🦋 ARGUMENTS 🦋

  • mdiodev — the mdio_device to be removed. this is the one getting removed. say bye 👋

💜 DESCRIPTION 💜

so like, this function is meant to be used as the .remove in an mdio_driver. that's its whole job, it's literally built for that field 🥹

first it unregisters the DSA switch — that part has to happen first, order matters, don't skip it — and then it calls the common remove function. clean, two-step, no drama 😌

🌈 CONTEXT 🌈

it can sleep 😴 so bestie, do not call this from somewhere that can't sleep. it's giving "process context energy" — respect it 💅

⭐ RETURN ⭐

nothing. zip. zero. void. it does the thing and comes back with empty hands 🫶

👑 SEE ALSO 👑

also quick vibe check: the functions listed here are realtek_mdio_probe(9) and realtek_mdio_shutdown(9), and the source file lives at ./drivers/net/dsa/realtek/realtek-mdio.c — go read it bestie, you'll learn something 🌸

and that's the whole page, periodt ✨ this one's from the ./drivers/net/dsa/realtek source, dated October 2026 — so if you're reading it in the future, hiiii 👋 congrats on the time travel, mwah 💖

📦 where this page comes from