_scsih_sas_b...mitive_event(9)

📦 version 7.3.1, in nixpkgs unstable

💅 _scsih_sas_b...mitive_event(9) — bestie, welcome to the Kernel API Manual 💅

okay so this page is short and sweet and honestly kind of iconic for it. It's from the Kernel API Manual, the page is _scsih_sas_b...mitive_event(9), and yes the title is truncated like that — no, we're not fixing it, that's just how it's giving. 💀 Let's go.

✨ NAME ✨

_scsih_sas_broadcast_primitive_event — handle broadcast events 🫶

that's it. that's the whole name. handle broadcast events. slay.

🎀 SYNOPSIS 🎀

void _scsih_sas_broadcast_primitive_event (struct MPT3SAS_ADAPTER *ioc ,
       struct fw_event_work *fw_event );

returns void, takes two things, zero drama. ✨

🌸 ARGUMENTS 🌸

  • ioc — per adapter object 💖 (the adapter's own lil object, like its whole personality)
  • fw_event — The fw_event_work object 🌟 (the firmware event itself, packaged up and ready to party)

🦋 CONTEXT 🦋

user. 🫶 that's literally the whole note. user context. noted. no further questions.

👑 SEE ALSO 👑

okay bestie buckle up because this list is long and it ate. The source of all this lore lives in the kernel file ./drivers/scsi/mpt3sas/mpt3sas_scsih.c, and then there's the extended universe:

like?? that's a lot of cross-references and every single one is here, no cap. click through them all or don't, i'm not your mom. 💜

and that's the page bestie!! short page, giant SEE ALSO, main character energy fr fr. 🌈 this whole thing lives under ./drivers/scsi/mpt3sas, dated October 2026 — so go read the docs, stay hydrated, and remember: user context. 🎀💖✨

📦 where this page comes from