STRUCT SL_WH_SCSI_TRIGGERS_T(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… 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_T structures 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