idpf_send_destroy_vport_msg(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– idpf_send_destroy_vport_msg πŸ’–

okay so welcome to the Kernel API Manual entry for idpf_send_destroy_vport_msg(9), bestie. this one is short and sweet β€” it's the send-virtchnl-destroy-vport-message situation, and we're keeping every crumb. no cap. 🫢


🌸 NAME 🌸

idpf_send_destroy_vport_msg β€” Send virtchnl destroy vport message

like, literally that. the function is idpf_send_destroy_vport_msg, and its whole name-section vibe is β€œSend virtchnl destroy vport message.” iconic. ✨


πŸŽ€ SYNOPSIS πŸŽ€

int idpf_send_destroy_vport_msg (struct idpf_adapter *adapter , u32
       vport_id );

this is the exact signature, so don’t come for me about the spacing β€” it’s giving manual-page realness. πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • adapter β€” adapter pointer used to send virtchnl message. that’s the adapter pointer, bestie, and it’s used to send the virtchnl message πŸ’…
  • vport_id β€” vport identifier used while preparing the virtchnl message. this is the vport identifier, and it gets used while preparing the virtchnl message ✨

πŸ”₯ RETURN πŸ”₯

0 on success, negative on failure. that’s the whole return situation: 0 means success, negative means failure. slay when it’s 0, sad girl hours when it’s negative 😭.


πŸ‘‘ SEE ALSO πŸ‘‘

the whole friend group is here, and yes, every single reference is invited. no cap, no cuts: 🫢


xoxo, your kernel bestie πŸ’– β€” this page comes from ./drivers/net/ethernet/intel/idpf, and it’s dated October 2026. it is, of course, the idpf_send_destroy_vport_msg(9) page. periodt ✨

πŸ“¦ where this page comes from