fc_rport_t0_prli(9)

🌸 NAME 🌸

okay so this is fc_rport_t0_prli(9) from the Kernel API Manual — the function that handles incoming PRLI parameters for type 0. That's the vibe, bestie. 💅

✨ SYNOPSIS ✨

The signature, literally exactly as it is:

int fc_rport_t0_prli (struct fc_rport_priv *rdata , u32 spp_len , const
       struct fc_els_spp *rspp , struct fc_els_spp *spp );

🎀 ARGUMENTS 🎀

• rdata — remote port private. It's the private data for the remote port, no cap.
• spp_len — service parameter page length, aka how long the service parameter page is. 📏
• rspp — received service parameter page. The one that came in. 👀
• spp — response service parameter page. The one for the response. ✨

🔗 SEE ALSO 🔗

Kernel file ./drivers/scsi/libfc/fc_rport.c — and here's the whole crew, no skips, fr fr:

• fc_rport_lookup(9)
• fc_rport_create(9)
• fc_rport_destroy(9)
• fc_rport_state(9)
• fc_set_rport_loss_tmo(9)
• fc_plogi_get_maxframe(9)
• fc_rport_state_enter(9)
• fc_rport_work(9)
• fc_rport_login(9)
• fc_rport_enter_delete(9)
• fc_rport_logoff(9)
• fc_rport_enter_ready(9)
• fc_rport_timeout(9)
• fc_rport_error(9)
• fc_rport_error_retry(9)
• fc_rport_login_complete(9)
• fc_rport_flogi_resp(9)
• fc_rport_enter_flogi(9)
• fc_rport_recv_flogi_req(9)
• fc_rport_plogi_resp(9)
• fc_rport_enter_plogi(9)
• fc_rport_prli_resp(9)
• fc_rport_enter_prli(9)
• fc_rport_rtv_resp(9)
• fc_rport_enter_rtv(9)
• fc_rport_recv_rtv_req(9)
• fc_rport_logo_resp(9)
• fc_rport_enter_logo(9)
• fc_rport_adisc_resp(9)
• fc_rport_enter_adisc(9)
• fc_rport_recv_adisc_req(9)
• fc_rport_recv_rls_req(9)
• fc_rport_recv_els_req(9)
• fc_rport_recv_req(9)
• fc_rport_recv_plogi_req(9)
• fc_rport_recv_prli_req(9)
• fc_rport_recv_prlo_req(9)
• fc_rport_recv_logo_req(9)
• fc_rport_flush_queue(9)
• fc_rport_fcp_prli(9)
• fc_setup_rport(9)
• fc_destroy_rport(9)
• fc_rport_terminate_io(9)

xoxo from the source/version ./drivers/scsi/libfc, dated October 2026 — fc_rport_t0_prli(9) out 💖🦋💅