fcoe_ctlr_vn_add(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ‘‘ fcoe_ctlr_vn_add β€” a kernel API girly pop πŸ’…

okay so bestie, this is a page from the Kernel API Manual section (9), and the star of the show is fcoe_ctlr_vn_add. Buckle up πŸŽ€


✨ NAME ✨

fcoe_ctlr_vn_add β€” add a VN2VN entry to the list, based on a claim reply πŸ’–

like literally that's the whole vibe. it adds a VN2VN entry to the list, and it does it based on a claim reply. periodt.


🌸 SYNOPSIS 🌸

void fcoe_ctlr_vn_add (struct fcoe_ctlr *fip , struct fcoe_rport *new );

no cap, that's character-for-character how it's written. spaces and all. we respect the source 🫢


πŸ¦‹ ARGUMENTS πŸ¦‹

  • fip β€” the FCoE controller. it's giving main character energy, honestly πŸ‘‘
  • new β€” a newly-parsed FCoE rport, serving as the template for the new rdata 🌱

πŸ’€ DESCRIPTION πŸ’€

so here's the thing β€” this one gets called with ctlr_mutex held. that's it, that's the note. locking discipline is not a drill, bestie πŸ”’βœ¨


🌈 SEE ALSO 🌈

the kernel file is ./drivers/scsi/fcoe/fcoe_ctlr.c, and it comes with a whole friend group of related functions. all of them. every single one. iykyk πŸ’…

bestie be honest, that's a lot of friends. but you can't skip any of them, they'd notice 😭

okay that's the whole page, mwah πŸ’‹ this one lives in ./drivers/scsi/fcoe, and it's dated October 2026, and the page answers to the name fcoe_ctlr_vn_add(9) β€” slay, go read the sibling pages, they ate 🌟

πŸ“¦ where this page comes from