iavf_init_s...vlan_v2_caps(9)

📦 version 7.3.1, in nixpkgs unstable

💅 NAME 💅

okay bestie, gather round — this is iavf_init_send_offload_vlan_v2_caps and it's literally part of initializing VLAN V2 caps, no cap. we're in the Kernel API Manual, section 9, and this page is a whole little moment. 🫶

✨ SYNOPSIS ✨

void iavf_init_send_offload_vlan_v2_caps (struct iavf_adapter *adapter);

🫶 ARGUMENTS 🫶

  • adapter — the board private structure. that's the whole vibe, she's just the board's private little structure and we're passing her in. main character energy fr. 💖

🎀 DESCRIPTION 🎀

so what does she do. this function processes the send of the extended VLAN V2 capability message on over to the PF. that's the task. that's the assignment. ✨

but here's the part you cannot skip, bestie, listen up 👑: it must clear IAVF_EXTENDED_CAP_RECV_VLAN_V2 if the message is not sent — for example when the PF isn't negotiating VIRTCHNL_VF_OFFLOAD_VLAN_V2. so no send = that flag gets cleared, periodt. don't leave it hanging, that's the rule. 🫡

ngl the "must" in there is doing a lot of work — it's giving mandatory-cleanup, not optional-vibes. 💀

🌈 SEE ALSO 🌈

no seriously, the squad is huge, this section ate and left no crumbs. also shoutout to the kernel file ./drivers/net/ethernet/intel/iavf/iavf_main.c 🦋 — and here's every single friend, in order:

and that's the page, bestie 💜 — brought to you by the lovely people over at ./drivers/net/ethernet/intel/iavf, dated October 2026. go clear that flag, ily, bye! 🌸🎀🦋

📦 where this page comes from