mpi3mr_sas_port_remove(9)
π mpi3mr_sas_port_remove(9) β the kernel api manual, but make it cute π
okay so bestie, welcome to the mpi3mr_sas_port_remove(9) page β it lives in the Kernel API Manual and it's short, sweet, and honestly kind of iconic for how little it does. ngl the whole thing is basically "bye, port π". let's go β¨
β¨ NAME β¨
mpi3mr_sas_port_remove β remove port from the list. that's it. that's the whole vibe π«Ά
πΈ SYNOPSIS πΈ
void mpi3mr_sas_port_remove (struct mpi3mr_ioc *mrioc , u64 sas_address
, u64 sas_address_parent , struct mpi3mr_hba_port *hba_port );
it returns void, so likeβ¦ don't @ it expecting a value back, it's not that kind of function π
π¦ ARGUMENTS π¦
these are the four things you gotta hand over, no cap:
mriocβ the adapter instance reference. think of it as the main character of this whole file πsas_addressβ the SAS address of the attached device. yes, the device. the one you're about to say goodbye to πsas_address_parentβ the SAS address of the parent expander or host. the parental figure, basically π§hba_portβ the HBA port entry. it's coming with you π
π DESCRIPTION π
okay so here's the tea: this thing removes the object and frees the associated memory from the sas_port_list. literally two jobs, both slaying β¨
so like β object gone, memory freed, list updated. clean. efficient. main character energy π
π RETURN π
None π
yeah. nothing. no return value. it just does the thing and dips. iykyk π
β SEE ALSO β
if you're the kind of person who clicks every link in the group chat, this section was made for you. everything below is the rest of the crew, and the source file itself is:
Kernel file ./drivers/scsi/mpi3mr/mpi3mr_transport.c
and now the whole squad, fr fr:
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)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 the whole friend group right there π₯
okay that's the page!! mwah π this manual page comes to you from ./drivers/scsi/mpi3mr and it's dated October 2026 β put it in your calendar bestie, and see you at the next mpi3mr function π¦β¨π
π¦ 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