STRUCT LEAPRAID_SCAN_DEV_DESC(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… struct leapraid_scan_dev_desc β€” Kernel API Manual ✨

okay so bestie, buckle up, because this is the page for struct leapraid_scan_dev_desc β€” the scan device descriptor for LeapRAID πŸŽ€. yes, that LeapRAID. it's a little bookkeeping struct that keeps track of like... whether scanning happened, whether it worked, whether the driver is still loading. very "group project where everyone needs to know what's going on" energy. lowkey essential, highkey underrated πŸ‘‘

You're reading a page from the Kernel API Manual, section 9. section 9 is for kernel routines, iykyk 🧚


✨ SYNOPSIS ✨

the whole vibe, verbatim, no cap:

struct leapraid_scan_dev_desc {
    u8 wait_scan_dev_done;
    u8 driver_loading;
    wait_queue_head_t wait_driver_loading;
    u8 first_scan_dev_fired;
    u8 scan_dev_failed;
    u8 scan_start;
    u16 scan_start_failed;
 };

look at all those u8s. adorable. it's giving "one byte is all I need" πŸ“


🌸 Members 🌸

okay so here's the actual tea on each field β€” the manpage documents exactly these six, and every one of them is a flag or a counter, which is honestly so on brand:

  • wait_scan_dev_done β€” flag indicating if scan device operation is done βœ… (the "are we there yet" of the struct)
  • driver_loading β€” flag indicating if driver is loading 🚚 (yes, the driver is still moving in, give her a minute)
  • first_scan_dev_fired β€” flag indicating if first scan device operation fired πŸ”₯ (the first one! the debut! main character energy)
  • scan_dev_failed β€” flag indicating if scan device operation failed πŸ’€ (the sad one. we don't talk about it, but we do document it)
  • scan_start β€” flag indicating if scan operation started 🏁 (has it kicked off? yes or no, no in-between)
  • scan_start_failed β€” count of failed scan start operations 😭 (a u16, so it can count a lot of bad days)
πŸ’‘ tiny heads-up: the struct up top also has wait_queue_head_t wait_driver_loading in it, but the Members list above doesn't document it. i'm not gonna make up a description for it because that would be lying, and we don't lie about kernel internals, bestie 🫢

πŸ¦‹ SEE ALSO πŸ¦‹

the full squad. all of them. no skips, no cuts, every single one, periodt ✨ this is the whole LeapRAID friend group and they're literally all in the same header file: ./drivers/scsi/leapraid/leapraid_func.h πŸ“

  • 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_overheat_desc(9)
  • struct leapraid_reset_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)

and that's the whole page, bestie πŸ’– big slay, tiny struct. this cutie lives over in ./drivers/scsi/leapraid πŸ—‚οΈ and this edition dropped October 2026 πŸ“… β€” six whole flags of pure bookkeeping excellence. go read the neighbors, they're iconic too πŸ‘‘πŸŒˆβ­

πŸ“¦ where this page comes from