fc_ct_fill(9)

🦋 fc_ct_fill(9) — Kernel API Manual 🦋

🌸 NAME 🌸

fc_ct_fill — fill in a common transport service request frame. That’s the whole assignment, bestie: it fills in a common transport service request frame. Slay. 💅

✨ SYNOPSIS ✨

okay so here’s the function signature, character for character, no edits, no cap:

int fc_ct_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 , u32
*did );

🎀 ARGUMENTS 🎀

• lport — your local port. Hiiii, local port 👋💖
• fc_id — the FC_ID of a non-destination rport, for GPN_ID and similar inquiries 👀
• fp — the frame that’s gonna contain the payload 📦✨
• op — the CT opcode, periodt.
• r_ctl — pointer to the FC header R_CTL 🎯
• fh_type — pointer to the FC-4 type 🌈
• did — the original literally says -- undescribed --, so no invented lore here, bestie 🙈. We are not making stuff up today.

🔥 SEE ALSO 🔥

The kernel file is ./drivers/scsi/libfc/fc_encode.h, and the whole linked squad is:

• fc_adisc_fill(9)
• fc_ct_hdr_fill(9)
• fc_ct_ns_fill(9)
• fc_ct_ms_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)

Source path ./drivers/scsi/libfc, date October 2026, page fc_ct_fill(9) — mwah, bestie, go hydrate 💖🦋