phylink_disconnect_phy(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

Okay bestie, so in the phylink_disconnect_phy(9) manual page (yes, the whole thing is literally named after the function, iconic naming tbh), we're talking about ✨unlinking a PHY✨. That's the whole vibe. Let me break it down for you 🫢


✨ NAME ✨

phylink_disconnect_phy β€” disconnect any PHY attached to the phylink instance.

Like, imagine the PHY and the phylink were holding hands 🀝 and this function is the "we need to talk" text. That's it. That's the function.


🌸 SYNOPSIS 🌸

void phylink_disconnect_phy (struct phylink *pl );

No return value, no drama, no notes. It just does the thing and leaves πŸ’…


πŸŽ€ ARGUMENTS πŸŽ€

  • pl β€” a pointer to a struct phylink returned from phylink_create. Bestie. Please make sure it's actually a valid one that came out of phylink_create. That's the assignment. That's the whole requirement. πŸ¦‹

πŸ’– DESCRIPTION πŸ’–

Disconnect any current PHY from the phylink instance described by pl.

That's the tea β˜• β€” whatever PHY is currently attached to that phylink instance, it gets disconnected. No cap, that's the entire behavior. Lowkey the most straightforward function in the whole phylink cinematic universe 🌈


πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./drivers/net/phy/phylink.c β€” aka the mothership πŸ›Έ β€” plus the entire phylink friend group, all present and accounted for:

Like I said. The whole friend group. Go read all of them, iykyk πŸ‘‘


🧚 Friendly reminder: this is the disconnect one. If you're trying to attach a PHY instead, you want phylink_connect_phy(9) or one of its cousins up there. Don't mix them up bestie, that's a whole different fanfic 😭

That's the page!! Sourced straight from ./drivers/net/phy, dated October 2026, and it's phylink_disconnect_phy(9) forever and always 🌟 Mwah, go disconnect responsibly πŸ’œ

πŸ“¦ where this page comes from