STRUCT LEAPRAID_FW_EVT_STRUCT(9)
π struct leapraid_fw_evt_struct(9) β the firmware-event glow-up π
okay so bestie, welcome to the Kernel API Manual entry for struct leapraid_fw_evt_struct, aka the little control room where firmware events get handled. no cap, this is the whole vibe. π
β¨ NAME β¨
struct leapraid_fw_evt_struct β the firmware event handling structure. that's it, that's the whole personality. she handles firmware events. she's booked and busy. π
π¦ SYNOPSIS π¦
here's the whole struct, character for character, because we do not paraphrase code in this house:
struct leapraid_fw_evt_struct {
u32 leapraid_evt_masks[4];
struct workqueue_struct *fw_evt_thread;
spinlock_t fw_evt_lock;
struct list_head fw_evt_list;
struct leapraid_fw_evt_work *cur_evt;
struct task_struct *cur_evt_task;
u8 fw_evt_cleanup;
};
look at her. seven members. main character energy fr fr. π
πΈ Members πΈ
okay so let's go member by member, iykyk:
leapraid_evt_masksβ an array of event masks, and she's literally<italic>four</italic>wide ([4]!), used for filtering firmware events. the bouncer at the club. β¨fw_evt_threadβ the workqueue used for processing firmware events. this is where the events actually get their work done. she's the group chat admin. πfw_evt_lockβ a spinlock protecting access to the firmware event list. do not touch the list without her. she's giving security guard. πfw_evt_listβ a linked list of pending firmware events. the queue of everyone waiting to be seen. πcur_evtβ pointer to the currently processing firmware event. the one whose turn it is. main character of the moment. βcur_evt_taskβ the task currently executing thecur_evtwork. she's the one doing the actual labor. respect her. π«Άfw_evt_cleanupβ a flag indicating whether cleanup of events is in progress. it's au8, it's tiny, it's doing its best. π§
π SEE ALSO π
bestie, buckle up, because this list is long and i'm obsessed. first up, the kernel file that has the receipts:
Kernel file ./drivers/scsi/leapraid/leapraid_func.h
and then, the whole extended family β all of them, no skipping, i promised:
struct leapraid_adapter_features(9)struct leapraid_adapter_attr(9)struct leapraid_io_req_tracker(9)struct leapraid_task_tracker(9)struct leapraid_rep_desc_maint(9)struct leapraid_rep_desc_seg_maint(9)struct leapraid_mem_desc(9)enum LEAPRAID_CB_INDEX(9)struct leapraid_default_reply(9)struct leapraid_sense_buffer(9)struct leapraid_driver_cmd(9)struct leapraid_driver_cmds(9)struct leapraid_dynamic_task_desc(9)struct leapraid_fw_evt_work(9)struct leapraid_rq(9)struct leapraid_int_rq(9)struct leapraid_blk_mq_poll_rq(9)struct leapraid_notification_desc(9)struct leapraid_overheat_desc(9)struct leapraid_reset_desc(9)struct leapraid_scan_dev_desc(9)struct leapraid_access_ctrl(9)struct leapraid_fw_log_desc(9)struct leapraid_card_port(9)struct leapraid_card_phy(9)struct leapraid_topo_node(9)struct leapraid_dev_topo(9)struct leapraid_boot_dev(9)struct leapraid_boot_devs(9)struct leapraid_adapter(9)struct leapraid_enc_node(9)struct leapraid_raid_volume(9)struct leapraid_starget_priv(9)struct leapraid_sdev_priv(9)struct leapraid_sas_dev(9)struct leapraid_sas_port(9)struct leapraid_vphy(9)struct leapraid_tgt_rst_list(9)struct sense_info(9)struct leapraid_fw_log_info(9)enum reset_type(9)struct leapraid_card_port_feature(9)
like, genuinely, go read them. they all ate. π₯
and that's the page, bestie!! π this came from the ./drivers/scsi/leapraid source, dated October 2026, and it lives in the Kernel API Manual as struct leap...w_evt_struct(9) (the terminal truncates her name, she's dramatic like that β¨). go forth and handle those firmware events. periodt. π¦π
π¦ 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