wx_check_for_rst_vf(9)

💅 wx_check_for_rst_vf(9) 💅

ok so bestie, welcome to the Kernel API Manual — yes we're in that part of the tree today, and honestly? iconic behaviour. this one's a little vibe check for the VF side of things: wx_check_for_rst_vf — checks to see if the PF has reset. that's it. that's the whole gig. 🎀

---

✨ NAME ✨

wx_check_for_rst_vf — checks to see if the PF has reset 🦋

like literally, the VF is peeking over at the PF like "hey… you good? did you reset on me?" and this function is the one asking. main character energy fr fr.

---

🌸 SYNOPSIS 🌸

int wx_check_for_rst_vf (struct wx *wx );

ngl keep that exact spacing, wx ) and all — we don't "fix" the source around here, we respect it 💖

---

🧚 ARGUMENTS 🧚

• wx — pointer to the HW structure. that's your hardware bestie, the whole structure, not a copy, not a vibe, a pointer. handle with care 🫶

---

⭐ RETURN ⭐

• returns 0 if the PF has set the reset done ✅ slay, we're so back
• returns -EBUSY on failure 😭 busy busy busy, try again later

lowkey important: 0 = reset done, -EBUSY = nope. don't mix them up or you'll be debugging at 3am, and not in a fun way 💀

---

🔥 SEE ALSO 🔥

the whole friend group, no cap — every single one of these is in the kernel file ./drivers/net/ethernet/wangxun/libwx/wx_mbx.c:

• wx_obtain_mbx_lock_pf(9)
• wx_check_for_ack_pf(9)
• wx_check_for_msg_pf(9)
• wx_write_mbx_pf(9)
• wx_read_mbx_pf(9)
• wx_check_for_rst_pf(9)
• wx_obtain_mbx_lock_vf(9)
• wx_check_for_ack_vf(9)
• wx_check_for_msg_vf(9)
• wx_poll_for_msg(9)
• wx_poll_for_ack(9)
• wx_read_posted_mbx(9)
• wx_write_posted_mbx(9)
• wx_write_mbx_vf(9)
• wx_read_mbx_vf(9)

like, the PF ones and the VF ones are literally siblings and they ate 💅

---

and that's the page bestie!! no notes, 10/10, would read again 🌈👑

mwah 💜 — this lil moment came to you from ./drivers/net/ethernet/wangxun..., dated October 2026, and yes the header said wx_check_for_rst_vf(9) twice because it's that confident. periodt. ✨