__fc_linkup(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– __fc_linkup(9) β€” the Kernel API Manual, but make it make sense πŸ¦‹

okay so bestie, welcome to the Kernel API Manual ✨ and today's main character is __fc_linkup, which is literally the handler for transport linkup events. that's the whole vibe. one function, one job, and she ate πŸ’…


🌸 NAME 🌸

__fc_linkup β€” handler for transport linkup events, no cap

like fr fr, when the transport link decides to come back up, this is the function that gets the call 🫢


✨ SYNOPSIS ✨

void __fc_linkup (struct fc_lport *lport );

she returns void, she takes one argument, she's lowkey iconic for that πŸŽ€


🧚 ARGUMENTS 🧚

  • lport β€” the lport whose link is up. that's it. that's the whole parameter. she's the one going through it, and you're handing her over so the linkup gets handled πŸ’œ

πŸ’€ SEE ALSO πŸ’€

okay buckle up because this list is long, bestie. iykyk 😭 everything here lives around Kernel file ./drivers/scsi/libfc/fc_lport.c β€” go read all of it, i'm not joking:


and that's the page, bestie 🫢 go handle that linkup. πŸ’–

🌈 cute sign-off time: this lil beauty ships from ./drivers/scsi/libfc, dated October 2026, and yeah β€” she's still __fc_linkup(9) at the bottom, forever our girl πŸ‘‘β­
πŸ“¦ where this page comes from