fc_rport_rtv_resp(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– fc_rport_rtv_resp πŸ’–

okay bestie, this is from the Kernel API Manual, and we're talking about fc_rport_rtv_resp β€” no cap, it's a whole vibe ✨

πŸ’– NAME πŸ’–

fc_rport_rtv_resp β€” Handler for Request Timeout Value (RTV) responses 🫢

✨ SYNOPSIS ✨

void fc_rport_rtv_resp (struct fc_seq *sp , struct fc_frame *fp , void
       *rdata_arg );

πŸŽ€ ARGUMENTS πŸŽ€

  • sp β€” The sequence the RTV was on, periodt πŸ’…
  • fp β€” The RTV response frame, literally the frame itself 🌸
  • rdata_arg β€” The remote port that sent the RTV response πŸ‘‘

πŸ¦‹ DESCRIPTION πŸ¦‹

Many targets don't seem to support this. lowkey that's the tea 😭

Locking Note: This function will be called without the rport lock held, but it will lock, call an _enter_* function or fc_rport_error and then unlock the rport. bestie, that lock choreography is not optional πŸ’€

🌈 SEE ALSO 🌈


mwah πŸ’‹ this page's source/version is ./drivers/scsi/libfc, dated October 2026, and it's the fc_rport_rtv_resp(9) manual page. bye bestie πŸ«ΆπŸ’–

πŸ“¦ where this page comes from