dp83tg720_c...t_get_status(9)

💅 dp83tg720_cable_test_get_status — Kernel API Manual

okay so bestie, you know how the header of this page says dp83tg720_c...t_get_status(9)? That's just the truncated little nickname for dp83tg720_cable_test_get_status, and this whole page lives under the Kernel API Manual umbrella. Cute. Let's get into it 🎀

---

✨ NAME ✨

dp83tg720_cable_test_get_status — the glow-up check for the cable test on the DP83TG720 PHY. She tells you whether the test is done done, or still cooking. 🦋

---

🌸 SYNOPSIS 🌸

int dp83tg720_cable_test_get_status (struct phy_device *phydev , bool *finished );

---

💖 ARGUMENTS 💖

• phydev — a pointer to the phy_device structure. Basically your ticket to the PHY, no PHY no party 🫶
• finished — a pointer to a bool that says whether the test is finished. Yes, it's a pointer, so she writes into your variable, she doesn't just gossip about it 💅

---

🧚 DESCRIPTION 🧚

The function sets the finished flag to true if the test is complete. That's the whole vibe check, ngl. Test done → flag goes true. Simple, iconic, no cap ✨

---

🔥 RETURN 🔥

0 on success, or a negative error code on failure. So if you get something negative back, that's your sign to go touch some grass and debug 😭

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/net/phy/dp83tg720.c
• dp83tg720_update_stats(9)
• dp83tg720_cable_test_start(9)
• dp83tg720_get_next_update_time(9)

Go read the whole little friend group, iykyk 💜

---

and that's the page, bestie! 🍓 this one's sourced from ./drivers/net/phy, stamped October 2026, and yeah the title up top still reads dp83tg720_c...t_get_status(9) because that's just the name she was given 💀✨