fc_fcp_recv_data(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

fc_fcp_recv_data(9)

okay so bestie, welcome to the Kernel API Manual side of the group chat πŸ’– this one is short and sweet, but it still has main-character energy.


✨ NAME ✨

fc_fcp_recv_data β€” the handler for receiving SCSI-FCP data from a target. literally that’s the vibe πŸŽ€


πŸŒ€ SYNOPSIS πŸŒ€

void fc_fcp_recv_data (struct fc_fcp_pkt *fsp , struct fc_frame *fp );

no cap, that’s the whole signature ⭐


πŸ’… ARGUMENTS πŸ’…

  • fsp β€” the FCP packet the data is on, like the little packet bestie carrying the moment πŸ’–
  • fp β€” the data frame, aka the frame with the data πŸ¦‹

πŸ‘€ SEE ALSO πŸ‘€

the whole linked-up friend group is right here, periodt:

Kernel file ./drivers/scsi/libfc/fc_fcp.c struct fc_fcp_internal(9),
fc_fcp_pkt_alloc(9), fc_fcp_pkt_release(9), fc_fcp_pkt_hold(9),
fc_fcp_pkt_destroy(9), fc_fcp_lock_pkt(9), fc_fcp_unlock_pkt(9),
fc_fcp_timer_set(9), fc_fcp_send_abort(9), fc_fcp_retry_cmd(9),
fc_fcp_ddp_setup(9), fc_fcp_ddp_done(9), fc_fcp_can_queue_ramp_up(9),
fc_fcp_can_queue_ramp_down(9), get_fsp_rec_tov(9), fc_fcp_send_data(9),
fc_fcp_abts_resp(9), fc_fcp_recv(9), fc_fcp_resp(9),
fc_fcp_complete_locked(9), fc_fcp_cleanup_cmd(9),
fc_fcp_cleanup_each_cmd(9), fc_fcp_abort_io(9), fc_fcp_pkt_send(9),
fc_fcp_cmd_send(9), fc_fcp_error(9), fc_fcp_pkt_abort(9),
fc_lun_reset_send(9), fc_lun_reset(9), fc_tm_done(9), fc_fcp_cleanup(9),
fc_fcp_timeout(9), fc_fcp_rec(9), fc_fcp_rec_resp(9),
fc_fcp_rec_error(9), fc_fcp_recovery(9), fc_fcp_srr(9),
fc_fcp_srr_resp(9), fc_fcp_srr_error(9), fc_fcp_lport_queue_ready(9),
fc_queuecommand(9), fc_io_compl(9), fc_eh_abort(9),
fc_eh_device_reset(9), fc_eh_host_reset(9), fc_sdev_init(9),
fc_fcp_destroy(9), fc_fcp_init(9)

xoxo, your Unix bestie πŸ’– β€” this page lives in ./drivers/scsi/libfc, and the date on the vibe check is October 2026 βœ¨πŸ‘‘

πŸ“¦ where this page comes from