mpi3mr_set_identify(9)
π mpi3mr_set_identify(9)
okay so bestie, we're deep in the kernel docs rn β this one lives in the Kernel API Manual, and it's literally all about setting up identify info for phys and end devices β¨
π NAME
mpi3mr_set_identify β set identify for phys and end devices
πΈ SYNOPSIS
int mpi3mr_set_identify (struct mpi3mr_ioc *mrioc , u16 handle , struct
sas_identify *identify );
π¦ ARGUMENTS
mriocβ the adapter instance reference, aka your whole controller's whole vibe πhandleβ the firmware device handle, the little name tag the firmware sticks on the deviceidentifyβ the SAS transport layer's identify info, i.e. the tea we're about to fill in π«Ά
π DESCRIPTION
Populates sas identify info for a specific device. that's it, that's the whole thing β it takes one specific device and gives its SAS identify info the glow-up it deserves β¨ no cap.
π RETURN
0 for success, non-zero for failure. (so likeβ¦ if you get a zero, you ate. anything else? not the vibe π)
β SEE ALSO
go bestie, go read the source:
- Kernel file
./drivers/scsi/mpi3mr/mpi3mr_transport.c
and the whole friend group π:
mpi3mr_post_transport_req(9)mpi3mr_report_manufacture(9)__mpi3mr_expander_find_by_handle(9)mpi3mr_is_expander_device(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_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)
k bye bestie, this page was brought to you by ./drivers/scsi/mpi3mr, dated October 2026, and it's literally called mpi3mr_set_identify(9) π
β¨ go read it again, iykyk
π¦ 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