STRUCT LEAPRAID_OVERHEAT_DESC(9)

💖 struct leapraid_overheat_desc(9) 💖

okay bestie, so this is a page from the Kernel API Manual (the title up top is all truncated as struct leap...verheat_desc(9), which is giving "the terminal ran out of room and gave up", but you already knew that) — and it's literally just the anatomy of one struct: struct leapraid_overheat_desc, aka the Overheat descriptor for LeapRAID 🔥. She's a little four-field girlie and every single member is iconic in her own way. Let's go. 🫶

---

✨ NAME ✨

struct leapraid_overheat_desc — the Overheat descriptor for LeapRAID. No cap, that's the whole job. 👑

---

🎀 SYNOPSIS 🎀

struct leapraid_overheat_desc {
    struct workqueue_struct *fault_overheat_wq;
    struct work_struct fault_overheat_work;
    atomic_t thermal_alert;
    char fault_overheat_wq_name[48];
 };

(the vibes are immaculate, the indentation is whatever the original said, we do not touch it 💅)

---

🦋 Members 🦋

• fault_overheat_wq — a struct workqueue_struct *, i.e. the workqueue for adapter thermal overheat operations. This is the queue where the hot-girl hot-problems get handled. 🌡️
• fault_overheat_work — a struct work_struct, the work structure for thermal overheat. This is the little task packet that actually gets queued up and run. 📬
• thermal_alert — an atomic_t, and it's a flag indicating if adapter thermal alert is active. She's atomic, so she's safe to poke from multiple places, and she's either "we're fine" or "we are literally cooking" 😭🔥
• fault_overheat_wq_name — a char array of size 48, the name of the fault overheat workqueue. Every workqueue deserves a cute name, and this is where hers lives. 🏷️✨

---

🌈 SEE ALSO 🌈

Kernel file ./drivers/scsi/leapraid/leapraid_func.h, plus the whole extended leapraid-verse, and yes, bestie, we're listing all of them because every single one is part of the family 🫶:

• 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_fw_evt_struct(9)
• struct leapraid_rq(9)
• struct leapraid_int_rq(9)
• struct leapraid_blk_mq_poll_rq(9)
• struct leapraid_notification_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)

---

okay and the sign-off, because we always credit the source: this page lives in ./drivers/scsi/leapraid and it's dated October 2026, with the footer calling it struct leap...verheat_desc(9) all over again. Stan a consistently truncated header, honestly. 💀🎀

stay cool (literally), don't overheat, and go read the rest of the leapraid structs 💜🦋⭐