iwlmld_kunit..._phy_of_link(9)

💜 iwlmld_kunit_get_phy_of_link(9) 💜

okay so this is a page straight out of the Kernel API Manual, section 9, and bestie it's a tiny one but it's important so stay with me 🫶

---

✨ NAME ✨

iwlmld_kunit_get_phy_of_link — get the phy of a link 🌸

like. the name is the whole plot. we love a self-describing function.

---

🎀 SYNOPSIS 🎀

struct iwl_mld_phy * iwlmld_kunit_get_phy_of_link (struct ieee80211_vif
*vif , u8 link_id );

that's it, that's the whole thing. two arguments in, a phy pointer out. iconic behavior honestly ✨

---

🦋 ARGUMENTS 🦋

• vif — the vif you're pulling the phy from, bestie. that's your starting point 💅
• link_id — the id of the link you want the phy for. you gotta know which link, no guessing 🎯

---

🌈 DESCRIPTION 🌈

so basically: you hand it a vif and a link_id, and it returns the phy pointer for that link. simple, clean, slay 💖

but — and this is the part where you gotta pay attention, ngl — this function assumes that the link actually exists, and that it already had a chanctx assigned to it. it is not out here doing vibe checks or defensive checks, it's just assuming 🙈

so if the link doesn't exist, or it never got a chanctx? the test will fail. no cap. this is not a hypothetical, that's literally what the page says 💀

---

👑 RETURN 👑

the phy pointer. that's the whole return value. a phy pointer. periodt 💅⭐

---

🧚 SEE ALSO 🧚

Kernel file ./drivers/net/wireless/intel/iwlwifi/mld/tests/utils.h

go read the actual file if you want the full picture, iykyk 🔥

---

a lil reminder before you go: vif + link_id → phy pointer, assuming the link exists AND had a chanctx assigned. those two assumptions are load-bearing, don't forget them 😭

---

kisses, this page came to you from ./drivers/net/wireless/intel/i... and it's dated October 2026 🎀💜 go forth and get your phy, bestie, you got this 🦋✨