of_phy_put(9)

📦 version 7.3.1, in nixpkgs unstable

💅 of_phy_put(9) — the Kernel API Manual, but make it cute ✨

Okay bestie, so we're in the Kernel API Manual today, and this little function is literally the "okay bye, thanks for the PHY" of the kernel world. It's short, it's sweet, and it's giving cleanup energy. Let's get into it 🫶

🌸 NAME 🌸

of_phy_put — release the PHY. That's it. That's the whole vibe. You're letting go, you're moving on, you're closing the tab 🦋

✨ SYNOPSIS ✨

void of_phy_put (struct phy *phy );

No return value, no drama, no notes. She's void and she's thriving 👑

🎀 ARGUMENTS 🎀

  • phy — the phy returned by of_phy_get. Yes, that one. The one you got earlier. Don't just grab any random struct phy * off the street, okay? This is a whole relationship, you have to keep track of the one you got 💖

🧚 DESCRIPTION 🧚

So here's the tea: of_phy_put releases a refcount that the caller received from of_phy_get. That's the entire function. It's a one-liner icon.

Think of it like this — when you called of_phy_get, you picked up a refcount. You were holding it. Possibly for a long time. Possibly forgetting about it. And now? Now you're putting it down. Responsible main character behavior 🔥

Not me holding refcounts I forgot to release 🙈 Bestie, that's how leaks happen. Don't be that girl.

👑 SEE ALSO 👑

Kernel file ./drivers/phy/phy-core.c, plus the whole PHY extended universe — because this function has so many siblings and honestly they all ate:

Like, the whole family reunion is in here. iykyk 💀

🌈 And that's the page, bestie! Sourced straight from ./drivers/phy, dated October 2026 — so go forth, put your PHYs back, and keep those refcounts balanced. Slay 💜✨
📦 where this page comes from