mpi3mr_get_...hy_error_log(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… mpi3mr_get_expander_phy_error_log β€” like, the whole vibe ✨

okay so bestie, welcome to the Kernel API Manual πŸŽ€ β€” yes, the same one, don't worry, you're in the right place. This page is all about mpi3mr_get_expander_phy_error_log, and ngl the name is a whole mouthful but we move πŸ’«


✨ NAME ✨

mpi3mr_get_expander_phy_error_log β€” return expander counters: πŸ’–

(yeah that's literally it, the colon is doing its own thing, we respect it 🫢)


🌸 SYNOPSIS 🌸

int mpi3mr_get_expander_phy_error_log (struct mpi3mr_ioc *mrioc , struct
phy );

look at her go 😭 she's returning an int, she's taking two args, she's iconic periodt πŸ‘‘


πŸ¦‹ ARGUMENTS πŸ¦‹

  • mrioc β€” the adapter instance reference πŸ’œ like, which adapter are we talking about, bestie? this is how you tell her.
  • phy β€” the SAS transport layer phy object 🌈 that's the pretty little phy creature we're pulling counters from.

⭐ RETURN ⭐

0 for success πŸŽ‰, non-zero for failure πŸ’€ β€” that's the whole deal, no cap. Zero means slay, anything else means uh oh πŸ™ˆ.

fr fr, if you get non-zero back, something went sideways β€” don't just ignore it, okay? 😭

πŸ‘‘ SEE ALSO πŸ‘‘

so like… there is a LOT of family here, and we're naming every single one of them because they all matter πŸ’…βœ¨

Kernel file ./drivers/scsi/mpi3mr/mpi3mr_transport.c 🌸

and then the entire group chat:

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_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_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 the whole friend group, and honestly every one of them ate πŸ”₯ iykyk πŸ’…


and that's the page, bestie!! 🌟 this one lives in ./drivers/scsi/mpi3mr, dated October 2026, and she answers to mpi3mr_get_...hy_error_log(9) πŸ’– go forth and check those expander phy counters, you absolute main character 🌈🫢✨

πŸ“¦ where this page comes from