mpi3mr_is_expander_device(9)
π mpi3mr_is_expander_device(9) β like, the whole vibe check for expanders β¨
okay so before we even get into it β this page lives in the Kernel API Manual, and the function is literally called mpi3mr_is_expander_device. yes bestie, it does exactly what it says on the tin π
β¨ NAME β¨
mpi3mr_is_expander_device β the little function that tells you if device is an expander π¦
πΈ SYNOPSIS πΈ
u8 mpi3mr_is_expander_device (u16 device_info );
that's it. one argument, one u8 back. lowkey elegant, ngl π
π ARGUMENTS π
device_infoβ a bitfield providing information about the device β¨ like, it's the little info packet you hand over so the function can peek inside and go "hmm π"
β RETURN β
1if the device is an expander device π0otherwise π
no cap, that's the entire return contract. binary queen behavior fr fr.
π¦ SEE ALSO π¦
first up, the kernel file where this all goes down:
./drivers/scsi/mpi3mr/mpi3mr_transport.cπ§
and then the whole friend group β all of these are (9) manpage girlies:
mpi3mr_post_transport_req(9)mpi3mr_report_manufacture(9)__mpi3mr_expander_find_by_handle(9)mpi3mr_get_sas_address(9)__mpi3mr_get_tgtdev_by_addr(9)mpi3mr_get_tgtdev_by_addr(9)mpi3mr_remove_device_by_sas_address(9)__mpi3mr_get_tgtdev_by_addr_and_rphy(9)mpi3mr_expander_find_by_sas_address(9)__mpi3mr_sas_node_find_by_sas_address(9)mpi3mr_parent_present(9)mpi3mr_convert_phy_link_rate(9)mpi3mr_delete_sas_phy(9)mpi3mr_add_sas_phy(9)mpi3mr_add_phy_to_an_existing_port(9)mpi3mr_delete_sas_port(9)mpi3mr_del_phy_from_an_existing_port(9)mpi3mr_sas_port_sanity_check(9)mpi3mr_set_identify(9)mpi3mr_add_host_phy(9)mpi3mr_add_expander_phy(9)mpi3mr_alloc_hba_port(9)mpi3mr_get_hba_port_by_id(9)mpi3mr_update_links(9)mpi3mr_sas_host_refresh(9)mpi3mr_sas_host_add(9)mpi3mr_sas_port_add(9)mpi3mr_sas_port_remove(9)struct host_port(9)mpi3mr_update_mr_sas_port(9)mpi3mr_refresh_sas_ports(9)mpi3mr_refresh_expanders(9)mpi3mr_expander_node_add(9)mpi3mr_expander_add(9)mpi3mr_expander_node_remove(9)mpi3mr_expander_remove(9)mpi3mr_get_sas_negotiated_logical_linkrate(9)mpi3mr_report_tgtdev_to_sas_transport(9)mpi3mr_remove_tgtdev_from_sas_transport(9)mpi3mr_get_port_id_by_sas_phy(9)mpi3mr_get_port_id_by_rphy(9)mpi3mr_get_expander_phy_error_log(9)mpi3mr_transport_get_linkerrors(9)mpi3mr_transport_get_enclosure_identifier(9)mpi3mr_transport_get_bay_identifier(9)mpi3mr_expander_phy_control(9)mpi3mr_transport_phy_reset(9)mpi3mr_transport_phy_enable(9)mpi3mr_transport_phy_speed(9)mpi3mr_map_smp_buffer(9)mpi3mr_unmap_smp_buffer(9)mpi3mr_transport_smp_handler(9)
like, that's a whole squad right there π«Ά go read them, iykyk π
and that's the whole page bestie β one arg, one bitfield, one iconic littleu8. check the device, get your1or0, move on with your life π
β¨ mwah β¨ this cutie came from ./drivers/scsi/mpi3mr, dated October 2026, and the source/version footer literally says mpi3mr_is_expander_device(9) β 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