STRUCT LEAPRAID_EVT_NOTIFY_REP(9)
π struct leapraid_evt_notify_rep(9) β like, the event notification reply, bestie
okay so this is a page straight out of the Kernel API Manual, and the star of the show is struct leapraid_evt_notify_rep β¨ (yes the header line got a lil' truncated in the wild, it's fine, we know her).
πΈ NAME πΈ
struct leapraid_evt_notify_rep β Event notification reply. that's it, that's the vibe. she replies. she notifies. she's an event π
π SYNOPSIS π
here's the whole layout, no cap, copied exactly:
struct leapraid_evt_notify_rep {
__le16 evt_data_len;
u8 msg_len;
u8 func;
u8 r1[2];
u8 r2;
u8 msg_flag;
u8 r3[6];
__le16 adapter_status;
u8 r4[4];
__le16 evt;
u8 r5[6];
__le32 evt_data[];
};
look at her. iconic. the reserved fields are literally just vibing there (r1 through r5, we see you) π«Ά
π¦ Members π¦
okay field-by-field tour, let's go:
evt_data_lenβ Length of event data. that's the number of bytes of event data, periodt.msg_lenβ Length of message.funcβ Function code.r1β Reserved. (not for you, bestie π)r2β Reserved.msg_flagβ Message flags.r3β Reserved.adapter_statusβ Adapter status.r4β Reserved.evtβ Event code.r5β Reserved.evt_dataβ Event data array. (it's a flexible array, she stretches as far as the event data needs π₯)
lowkey note: everything marked Reserved is exactly that β reserved. don't be out here reading or writing them like they're yours, fr fr π
π SEE ALSO π
the whole friend group, in order, all of them, no skipping π β and yeah, first up it's the Kernel file ./drivers/scsi/leapraid/leapraid.h:
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_scsi_tm_rep(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_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)
and that's the whole page, bestie, you ate that π this lil' beauty lives over in ./drivers/scsi/leapraid, dated October 2026, and it's page struct leapraid_evt_notify_rep(9) of the Kernel API Manual β go forth and read those reply structs with main character energy πβ¨
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms