STRUCT LEAPRAID_EVT_SAS_TOPO_PHY_ENTRY(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– struct leapraid_evt_sas_topo_phy_entry(9) πŸ’–

okay bestie, welcome to the Kernel API Manual β€” we’re looking at the SAS topology PHY entry and it’s honestly a tiny icon. No cap, it’s just three fields and a whole lot of main-character energy.

🌸 NAME 🌸

struct leapraid_evt_sas_topo_phy_entry β€” SAS topology PHY entry. That’s the whole name-and-desc combo, periodt.

✨ SYNOPSIS ✨

Here’s the struct exactly as it’s written, bestie:

struct leapraid_evt_sas_topo_phy_entry {
    __le16 attached_dev_hdl;
    u8 link_rate;
    u8 phy_status;
};

πŸ’… Members πŸ’…

  • attached_dev_hdl β€” device handle attached to PHY. Like, literally the handle for the device attached to the PHY.
  • link_rate β€” current link rate. The rate it’s linking at right now.
  • phy_status β€” PHY status flags. The flags that tell you the PHY’s status situation.

πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./drivers/scsi/leapraid/leapraid.h struct β€” that’s the header where this lives. And here are all the linked pages, every single one, no skipping:

  • struct leapraid_reg_base(9)
  • struct leapraid_atomic_req_desc(9)
  • union leapraid_rep_desc_union(9)
  • struct leapraid_req(9)
  • struct leapraid_rep(9)
  • struct leapraid_sge_simple32(9)
  • struct leapraid_sge_simple64(9)
  • struct leapraid_sge_simple_union(9)
  • struct leapraid_sge_chain_union(9)
  • struct leapraid_ieee_sge_simple32(9)
  • struct leapraid_ieee_sge_simple64(9)
  • union leapraid_ieee_sge_simple_union(9)
  • union leapraid_ieee_sge_chain_union(9)
  • struct leapraid_chain64_ieee_sg(9)
  • union leapraid_ieee_sge_io_union(9)
  • union leapraid_simple_sge_union(9)
  • union leapraid_sge_io_union(9)
  • struct leapraid_cfg_pg_header(9)
  • struct leapraid_cfg_ext_pg_header(9)
  • struct leapraid_cfg_req(9)
  • struct leapraid_cfg_rep(9)
  • struct leapraid_boot_dev_format_sas_wwid(9)
  • struct leapraid_boot_dev_format_enc_slot(9)
  • struct leapraid_boot_dev_format_dev_name(9)
  • union leapraid_boot_dev_format(9)
  • struct leapraid_manufacturing_p0(9)
  • struct leapraid_bios_page2(9)
  • struct leapraid_bios_page3(9)
  • struct leapraid_raidvol0_phys_disk(9)
  • struct leapraid_raidvol_p0(9)
  • struct leapraid_raidvol_p1(9)
  • struct leapraid_raidpd_p0(9)
  • struct leapraid_sas_io_unit0_phy_info(9)
  • struct leapraid_sas_io_unit_p0(9)
  • struct leapraid_exp_p0(9)
  • struct leapraid_exp_p1(9)
  • struct leapraid_sas_dev_p0(9)
  • struct leapraid_sas_phy_p0(9)
  • struct leapraid_enc_p0(9)
  • struct leapraid_raid_cfg_p0_element(9)
  • struct leapraid_raid_cfg_p0(9)
  • union leapraid_mpi_scsi_io_cdb_union(9)
  • struct leapraid_mpi_scsiio_req(9)
  • union leapraid_scsi_io_cdb_union(9)
  • struct leapraid_scsiio_req(9)
  • struct leapraid_scsiio_rep(9)
  • struct leapraid_scsi_tm_req(9)
  • struct leapraid_scsi_tm_rep(9)
  • struct leapraid_sep_req(9)
  • struct leapraid_sep_rep(9)
  • struct leapraid_adapter_init_req(9)
  • struct leapraid_rep_desc_q_arr(9)
  • struct leapraid_adapter_init_rep(9)
  • struct leapraid_adapter_log_req(9)
  • struct leapraid_adapter_log_rep(9)
  • struct leapraid_adapter_features_req(9)
  • struct leapraid_adapter_features_rep(9)
  • struct leapraid_scan_dev_req(9)
  • struct leapraid_scan_dev_rep(9)
  • struct leapraid_evt_notify_req(9)
  • struct leapraid_evt_notify_rep(9)
  • struct leapraid_evt_data_sas_dev_status_change(9)
  • struct leapraid_evt_data_ir_change(9)
  • struct leapraid_evt_data_sas_disc(9)
  • struct leapraid_evt_data_sas_topo_change_list(9)
  • struct leapraid_evt_data_sas_enc_dev_status_change(9)
  • struct leapraid_io_unit_ctrl_req(9)
  • struct leapraid_io_unit_ctrl_rep(9)
  • struct leapraid_raid_act_req(9)
  • struct leapraid_raid_act_rep(9)
  • struct leapraid_smp_passthrough_req(9)
  • struct leapraid_smp_passthrough_rep(9)
  • struct leapraid_sas_io_unit_ctrl_req(9)

okay that’s the page, mwah πŸ’‹ β€” source/version: ./drivers/scsi/leapraid; date: October 2026; footer title vibe: struct leapr...po_phy_entry(9). slay responsibly.

πŸ“¦ where this page comes from