fc_rport_recv_rls_req(9)

💖 NAME 💖

fc_rport_recv_rls_req — Handle received Read Link Status request

okay bestie, welcome to the fc_rport_recv_rls_req(9) page from the Kernel API Manual — yes, we’re in kernel-API-manual territory and it’s lowkey iconic. 💅

✨ SYNOPSIS ✨

void fc_rport_recv_rls_req (struct fc_rport_priv *rdata , struct
       fc_frame *rx_fp );

🎀 ARGUMENTS 🎀

• rdata — The remote port that sent the RLS request. That’s the sender, bestie. 🫶
• rx_fp — The PRLI request frame. Yep, the page says PRLI right here — keeping it exactly as written. 🙈

🌈 SEE ALSO 🌈

Kernel file: ./drivers/scsi/libfc/fc_rport.c

Also see: 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_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_rport_t0_prli(9), fc_setup_rport(9), fc_destroy_rport(9), fc_rport_terminate_io(9)

That’s the whole vibe, bestie — source/version: ./drivers/scsi/libfc; date: October 2026; page: fc_rport_recv_rls_req(9). Signed off with a sparkle. 🎀✨