fc_fill_reply_hdr(9)

💖 fc_fill_reply_hdr(9) — NAME 💖

okay so bestie, this is the fc_fill_reply_hdr(9) page from the Kernel API Manual, and it's literally about one thing: fc_fill_reply_hdr — fill FC reply header fields based on request. no cap. 💅

✨ SYNOPSIS ✨

here's the exact signature, bestie — do not freestyle it:

       void fc_fill_reply_hdr (struct fc_frame *fp , const struct fc_frame
       *in_fp , enum fc_rctl r_ctl , u32 parm_offset );

it's a void situation, so there's no return value to catch — it just does the header-filling thing. 🫶

🎀 ARGUMENTS 🎀

• fp — the reply frame containing the header to be filled in. this is the one getting its header moment, bestie.
• in_fp — the request frame containing the header to use in filling in the reply. it's the reference frame doing the supplying.
• r_ctl — the R_CTL value for the reply.
• parm_offset — the parameter / offset value. yes, parameter slash offset, exactly like that. 🍓

🔗 SEE ALSO 🔗

• Kernel file: ./drivers/scsi/libfc/fc_libfc.c
• libfc_init(9)
• libfc_exit(9)
• fc_copy_buffer_to_sglist(9)
• fc_fill_hdr(9)
• fc_fc4_conf_lport_params(9)
• fc_fc4_register_provider(9)
• fc_fc4_deregister_provider(9)
• fc_fc4_add_lport(9)
• fc_fc4_del_lport(9)

mwah 💋 that's the whole page, bestie. source/version: ./drivers/scsi/libfc, date: October 2026, and it's giving fc_fill_reply_hdr(9) energy. byeeee 🦋✨