fc_vport_id_lookup(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ fc_vport_id_lookup(9) ✨

okay bestie, welcome to the Kernel API Manual πŸ’– this one's a lil function called fc_vport_id_lookup, and honestly? it's giving matchmaker energy. you hand it a fabric ID and it goes looking for the NPIV lport that vibes with it. iykyk πŸŽ€


🌸 NAME 🌸

fc_vport_id_lookup β€” find the NPIV lport that matches a given fabric ID πŸ”πŸ’…

like, it's literally a lookup. you want the lport for this fabric ID? boom, here she is. main character energy fr fr 🌟


πŸ¦‹ SYNOPSIS πŸ¦‹

struct fc_lport * fc_vport_id_lookup (struct fc_lport *n_port , u32 port_id );

so she takes two things and gives you back a struct fc_lport * β€” no cap, that's the whole vibe check 🫢


πŸ’œ ARGUMENTS πŸ’œ

  • n_port β€” the top level N_Port which may have multiple NPIV VN_Ports πŸ§šβ€β™€οΈ think of it as the parent friend who's got a whole group chat of VN_Ports under her wing. this is the one you're searching within.
  • port_id β€” the fabric ID to find a match for 🎯 the thing you're hunting for. she's gonna go see who matches.

⭐ RETURN ⭐

matching lport pointer 🌈 β€” or NULL if there is no match πŸ˜­πŸ’€

fr fr, always check for NULL before you go dereferencing, bestie. no match means no match, and she will absolutely hand you a NULL and walk away πŸ’…

πŸŽ€ SEE ALSO πŸŽ€

all the sibling functions, the whole little libfc family reunion 🫢✨ go read them too, they're iconic in their own right πŸ‘‘


and that's the page, bestie!! πŸ¦‹ this lil slice of the Kernel API Manual (section 9, fc_vport_id_lookup(9) β€” yes she has her own number, queen behavior πŸ‘‘) lives down in ./drivers/scsi/libfc and the version/date on this one is October 2026. periodt. πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from