fc_host_fpin_rcv(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… fc_host_fpin_rcv ✨ Kernel API Manual πŸ¦‹

okay so bestie, welcome to the fc_host_fpin_rcv page πŸ’– this one's short and sweet and it lives in the Kernel API Manual, and honestly? it's giving "small function, big responsibility" energy πŸ‘‘


πŸŽ€ NAME πŸŽ€

fc_host_fpin_rcv β€” the routine that processes a received FPIN πŸ’« (no cap, that's literally the whole job)


🌸 SYNOPSIS 🌸

void fc_host_fpin_rcv (struct Scsi_Host *shost , u32 fpin_len , char
*fpin_buf , u8 event_acknowledge );

she takes four things, she returns void, she minds her own business 🫢


✨ ARGUMENTS ✨

  • shost β€” the host that the FPIN was received on πŸ–₯️ like, which host, bestie, we need to know
  • fpin_len β€” length of the FPIN payload, in bytes πŸ“ measured in bytes, not vibes
  • fpin_buf β€” pointer to the FPIN payload 🎯 the actual goods
  • event_acknowledge β€” 1, if LLDD handles this event πŸ™ˆ ok so set her to 1 when the LLDD is the one handling this event, periodt

🧚 NOTES 🧚

This routine assumes no locks are held on entry πŸ”’πŸ˜Œ like, walk in with your hands empty, bestie β€” no locks held, that's the whole vibe check.

fr fr, that's a real assumption, not a suggestion β€” no locks are held on entry when you call this πŸ’€

πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./drivers/scsi/scsi_transport_fc.c πŸ“ and a whole friend group of functions, all in their (9) era:

that's THIRTY-TWO functions, bestie, we counted, we love a thorough cross-reference πŸ’…


🫢 the sign-off 🫢

and that's the page!! mwah πŸ’‹ this little icon lives over in ./drivers/scsi, dated October 2026, and it's filed under fc_host_fpin_rcv(9) β€” go read her friends, they ate πŸŒˆβ­πŸ“

πŸ“¦ where this page comes from