STRUCT LEAPRAID_SCSI_TM_REP(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– struct leapraid_scsi_tm_rep(9) πŸ’–

okay bestie, welcome to the Kernel API Manual, section 9 β€” yes we're in the big-kid kernel docs today and honestly? iconic behavior. this page is all about struct leapraid_scsi_tm_rep, aka the SCSI Task Management response. it's giving "the receipt that comes back after you asked the adapter to do something about a task" πŸ’…


✨ NAME ✨

struct leapraid_scsi_tm_rep β€” SCSI Task Management response πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

struct leapraid_scsi_tm_rep {
    __le16 dev_hdl;
    u8 msg_len;
    u8 func;
    u8 resp_code;
    u8 task_type;
    u8 r1;
    u8 msg_flag;
    u8 r2[6];
    __le16 adapter_status;
    u8 r3[4];
    __le32 termination_count;
    __le32 response_info;
 };

like, there it is. the whole vibe in one struct. no cap, every field is required to be exactly that 🫢


🌸 Members 🌸

  • dev_hdl β€” the Device handle. it's literally the little name tag that says which device we're talking about πŸ’–
  • msg_len β€” Length of response message. how much message we're working with, bestie.
  • func β€” Function code. the "what are we even doing here" field ✨
  • resp_code β€” Response code. the answer. the verdict. the moment of truth.
  • task_type β€” Task management type. tells you which flavor of task management this response is about.
  • r1 β€” Reserved. hands off, it's not for you πŸ™ˆ
  • msg_flag β€” Message flags. the little extra vibes attached to the message.
  • r2 β€” Reserved. also not yours. moving on ✨
  • adapter_status β€” Adapter status. how the adapter itself is feeling about all this.
  • r3 β€” Reserved. (yes, another one β€” they come in packs, iykyk)
  • termination_count β€” Count of terminated tasks. lowkey the most dramatic field on the page πŸ’€πŸ”₯
  • response_info β€” Additional response info. the extra lore. the bonus content πŸŽ€

🧚 SEE ALSO 🧚

okay so this is the part where the kernel doc just lists the whole friend group, and honestly? slay. every single one of these, no skips, no cuts πŸ‘‘

  • the Kernel file ./drivers/scsi/leapraid/leapraid.h β€” that's the home base, bestie 🏠

and now the extended fam, in order, fr fr:

  • struct leapraid_reg_base(9)
  • struct leapraid_atomic_req_desc(9)
  • union leapraid_rep_desc_union(9)
  • struct leapraid_req(9)
  • struct leapraid_rep(9)
  • struct leapraid_sge_simple32(9)
  • struct leapraid_sge_simple64(9)
  • struct leapraid_sge_simple_union(9)
  • struct leapraid_sge_chain_union(9)
  • struct leapraid_ieee_sge_simple32(9)
  • struct leapraid_ieee_sge_simple64(9)
  • union leapraid_ieee_sge_simple_union(9)
  • union leapraid_ieee_sge_chain_union(9)
  • struct leapraid_chain64_ieee_sg(9)
  • union leapraid_ieee_sge_io_union(9)
  • union leapraid_simple_sge_union(9)
  • union leapraid_sge_io_union(9)
  • struct leapraid_cfg_pg_header(9)
  • struct leapraid_cfg_ext_pg_header(9)
  • struct leapraid_cfg_req(9)
  • struct leapraid_cfg_rep(9)
  • struct leapraid_boot_dev_format_sas_wwid(9)
  • struct leapraid_boot_dev_format_enc_slot(9)
  • struct leapraid_boot_dev_format_dev_name(9)
  • union leapraid_boot_dev_format(9)
  • struct leapraid_manufacturing_p0(9)
  • struct leapraid_bios_page2(9)
  • struct leapraid_bios_page3(9)
  • struct leapraid_raidvol0_phys_disk(9)
  • struct leapraid_raidvol_p0(9)
  • struct leapraid_raidvol_p1(9)
  • struct leapraid_raidpd_p0(9)
  • struct leapraid_sas_io_unit0_phy_info(9)
  • struct leapraid_sas_io_unit_p0(9)
  • struct leapraid_exp_p0(9)
  • struct leapraid_exp_p1(9)
  • struct leapraid_sas_dev_p0(9)
  • struct leapraid_sas_phy_p0(9)
  • struct leapraid_enc_p0(9)
  • struct leapraid_raid_cfg_p0_element(9)
  • struct leapraid_raid_cfg_p0(9)
  • union leapraid_mpi_scsi_io_cdb_union(9)
  • struct leapraid_mpi_scsiio_req(9)
  • union leapraid_scsi_io_cdb_union(9)
  • struct leapraid_scsiio_req(9)
  • struct leapraid_scsiio_rep(9)
  • struct leapraid_scsi_tm_req(9)
  • struct leapraid_sep_req(9)
  • struct leapraid_sep_rep(9)
  • struct leapraid_adapter_init_req(9)
  • struct leapraid_rep_desc_q_arr(9)
  • struct leapraid_adapter_init_rep(9)
  • struct leapraid_adapter_log_req(9)
  • struct leapraid_adapter_log_rep(9)
  • struct leapraid_adapter_features_req(9)
  • struct leapraid_adapter_features_rep(9)
  • struct leapraid_scan_dev_req(9)
  • struct leapraid_scan_dev_rep(9)
  • struct leapraid_evt_notify_req(9)
  • struct leapraid_evt_notify_rep(9)
  • struct leapraid_evt_data_sas_dev_status_change(9)
  • struct leapraid_evt_data_ir_change(9)
  • struct leapraid_evt_data_sas_disc(9)
  • struct leapraid_evt_sas_topo_phy_entry(9)
  • struct leapraid_evt_data_sas_topo_change_list(9)
  • struct leapraid_evt_data_sas_enc_dev_status_change(9)
  • struct leapraid_io_unit_ctrl_req(9)
  • struct leapraid_io_unit_ctrl_rep(9)
  • struct leapraid_raid_act_req(9)
  • struct leapraid_raid_act_rep(9)
  • struct leapraid_smp_passthrough_req(9)
  • struct leapraid_smp_passthrough_rep(9)
  • struct leapraid_sas_io_unit_ctrl_req(9)

ngl bestie, that's a lot of cross-references β€” but that's literally every single one, so you're fully covered πŸ’œ

and that's the whole page!! 🌈 one last cute little sign-off: this one lives over in ./drivers/scsi/leapraid, and it's stamped October 2026 β€” so yeah, future vibes, main character energy, periodt πŸ’…πŸŽ€βœ¨

πŸ“¦ where this page comes from