STRUCT SL_WH_SCSI_TRIGGERS_T(9)
π struct SL_WH_SCSI_TRIGGERS_T(9) β bestie, lemme introduce you β¨
okay so welcome to the Kernel API Manual π and today's main character is struct SL_WH_SCSI_TRIGGERS_T β no cap, it's a whole vibe.
πΈ NAME πΈ
struct SL_WH_SCSI_TRIGGERS_T β this is the structure that gets passed to/from sysfs, and it holds a list of SCSI sense codes. When one of those sense codes gets observed, it should trigger a DIAG_SERVICE event. that's literally the whole job π
π¦ SYNOPSIS π¦
struct SL_WH_SCSI_TRIGGERS_T {
uint32_t ValidEntries;
struct SL_WH_SCSI_TRIGGER_T SCSITriggerEntry[NUM_VALID_ENTRIES];
};
like, look at her. iconic. β¨
π Members π
ValidEntriesβ the number of_SL_WH_SCSI_TRIGGER_Tstructures contained in this structure. yes she's counting her own little family π«ΆSCSITriggerEntryβ the list of SCSI Sense Code trigger elements. this is the roster, the lineup, the squad π
π Description π
this binary structure gets transferred via sysfs so the Linux Driver can get/set SCSI Sense Code Triggers. that's it, that's the tea β β it's the little messenger shuttling your trigger data in and out π₯
β SEE ALSO β
go look at the kernel file ./drivers/scsi/mpt3sas/mpt3sas_trigger_diag.h β that's where the lore lives π and also check out her besties:
struct SL_WH_EVENT_TRIGGER_T(9)struct SL_WH_EVENT_TRIGGERS_T(9)struct SL_WH_SCSI_TRIGGER_T(9)struct SL_WH_MPI_TRIGGER_T(9)struct SL_WH_MPI_TRIGGERS_T(9)struct SL_WH_TRIGGERS_EVENT_DATA_T(9)
and that's the whole page, bestie β brought to you by ./drivers/scsi/mpt3sas, dated October 2026, living that struct SL_WH...I_TRIGGERS_T(9) life. slay, go read the source, ily ππ§ββοΈ
π¦ 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