fc_ct_ns_fill(9)

💅 fc_ct_ns_fill — bestie, it's giving "fill in a name service request frame"

Okay so real talk, we're in fc_ct_ns_fill(9) territory — that's the Kernel API Manual era of the kernel, and this lil function is literally just here to fill in a name service request frame. That's the whole vibe check. ✨

🌸 SYNOPSIS 🌸

int fc_ct_ns_fill (struct fc_lport *lport , u32 fc_id , struct fc_frame
*fp , unsigned int op , enum fc_rctl *r_ctl , enum fc_fh_type *fh_type
);

Like, look at that signature. Six whole arguments. She ate and left no crumbs. 👑

🎀 ARGUMENTS 🎀

• lport — local port. The homegirl. The main character. 🫶
• fc_id — the FC_ID of the non-destination rport, used for GPN_ID and similar inquiries. Not the destination, okay?? Don't get it twisted, bestie. 🙈
• fp — the frame that's gonna contain the payload. She's the container, she's doing the holding. 💖
• op — the CT opcode. That's it. That's the whole description. Iconic brevity honestly. ⭐
• r_ctl — a pointer to the FC header R_CTL. Pointer behavior, you know how it is. 💅
• fh_type — a pointer to the FC-4 type. Also a pointer. Siblings. 🌈

🦋 SEE ALSO 🦋

Like, the whole kernel file ./drivers/scsi/libfc/fc_encode.h is a family reunion of fill functions and you know we're listing every single one, no skips, no cuts. Periodt. 🔥

• fc_adisc_fill(9)
• fc_ct_hdr_fill(9)
• fc_ct_ms_fill(9)
• fc_ct_fill(9)
• fc_plogi_fill(9)
• fc_flogi_fill(9)
• fc_fdisc_fill(9)
• fc_logo_fill(9)
• fc_rtv_fill(9)
• fc_rec_fill(9)
• fc_prli_fill(9)
• fc_scr_fill(9)
• fc_els_fill(9)

Not one of them skipped, because we respect the lore. 💜

🌟 and that's the tea 🌟

This page lives in ./drivers/scsi/libfc, dated October 2026, and it's part of the Kernel API Manual — so yeah, that's the source, the version era, and the date all wrapped up in a cute lil bow. 🎀 Slay, go fill those frames, bestie. 🦋✨