fnic_fcoe_pr...s_flogi_resp(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 fnic_fcoe_process_flogi_resp 🌸

okay so bestie, this is a page from the Kernel API Manual β€” yes, the kernel manual, we're doing big-girl kernel hours πŸ’… β€” and it's all about one lil function called fnic_fcoe_process_flogi_resp. Buckle up, it's short and sweet.


✨ NAME ✨

fnic_fcoe_process_flogi_resp β€” literally the function that processes the FLOGI response from the FCF. that's it, that's the whole job 🫢


πŸ¦‹ SYNOPSIS πŸ¦‹

void fnic_fcoe_process_flogi_resp (struct fnic *fnic , struct fip_header
*fiph );

no return value, she just does things. void queen πŸ‘‘


πŸŽ€ ARGUMENTS πŸŽ€

  • fnic β€” Handle to the fnic driver instance. like, the actual driver vibe, the main character of this whole situation 🌈
  • fiph β€” Received frame. the frame that showed up. the mail, if you will πŸ’Œ

πŸ’– DESCRIPTION πŸ’–

okay so here's the tea β˜• β€” if it's successful, she saves the assigned fc_id and MAC, programs the firmware, and starts fdls discovery. iconic behaviour, no notes ✨

but if it's not successful? she restarts vlan discovery instead. different path, same determination πŸ’ͺ not me being emotionally invested in a FLOGI response 😭


πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./drivers/scsi/fnic/fip.c, plus the whole friend group β€” go say hi:


mwah πŸ’‹ this page lives in ./drivers/scsi/fnic and it's dated October 2026 β€” future-coded of her, honestly. stay slay, stay discovered, periodt πŸ§šβ€β™€οΈ

πŸ“¦ where this page comes from