fc_seq_start_next_locked(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… fc_seq_start_next_locked(9) β€” the Kernel API Manual page your group chat needed

okay so hear me out bestie, this is a page from the Kernel API Manual and it's genuinely so niche but so important, like it's giving "small function, big responsibilities" energy. grab a strawberry drink and let's get into it πŸ“βœ¨


✨ NAME ✨

fc_seq_start_next_locked β€” literally what it says on the tin: it allocates a new sequence on the same exchange as the supplied sequence. no cap, that's the whole vibe. πŸŽ€


🌸 SYNOPSIS 🌸

struct fc_seq * fc_seq_start_next_locked (struct fc_seq *sp );

that's it, that's the whole call. one argument, returns a pointer to a struct fc_seq. iconic and minimal πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • sp β€” the sequence/exchange you're asking to get a new sequence for. that's the one. that's who you're talking to. 🫢
ok real talk, this is the only argument, so if you fumble it there is nothing else to blame. no pressure tho πŸ’–

πŸ‘‘ SEE ALSO πŸ‘‘

okay so this part is a whole friend group. the manpage says Kernel file ./drivers/scsi/libfc/fc_exch.c, and then it just keeps going. we're listing all of them because nobody gets left behind, periodt:

like, that's a squad. read them all, iykyk πŸ’€πŸ”₯


πŸ’œ cute little sign-off: this page lives in ./drivers/scsi/libfc, and it's dated October 2026. so go forth, allocate that sequence, and slay πŸ§šβ€β™€οΈβ­πŸŒˆ
πŸ“¦ where this page comes from