mptsas_del_end_device(9)

💫 NAME 💫

mptsas_del_end_device — okay so this one literally just reports a deleted end device to the sas transport layer 🫶 that's the whole gig, no cap

✨ SYNOPSIS ✨

void mptsas_del_end_device (MPT_ADAPTER *ioc , struct mptsas_phyinfo
*phy_info );

Bestie look at that signature — void return, so she doesn't hand anything back, she just does the thing and dips 💅

🎀 ARGUMENTS 🎀

• ioc — Pointer to MPT_ADAPTER structure 👑 this is the adapter brain, the main character energy of the whole call
• phy_info — describes attached device 🦋 she's carrying the tea about which device is attached

🌸 SEE ALSO 🌸

Like, go read the actual kernel file if you want the real lore:

• Kernel file ./drivers/message/fusion/mptsas.c 📄

And the whole friend group, because mptsas functions literally travel in a pack:

• mptsas_find_portinfo_by_sas_address(9)
• mptsas_add_device_component(9)
• mptsas_add_device_component_by_fw(9)
• mptsas_add_device_component_starget_ir(9)
• mptsas_add_device_component_starget(9)
• mptsas_del_device_component_by_os(9)
• mptsas_del_device_components(9)
• mptsas_find_vtarget(9)
• mptsas_target_reset(9)
• mptsas_target_reset_queue(9)
• mptsas_schedule_target_reset(9)
• mptsas_taskmgmt_complete(9)
• mptsas_ioc_reset(9)
• enum device_state(9)
• mptsas_add_end_device(9)
• mptsas_firmware_event_work(9)
• mptsas_eh_timed_out(9)
• mptsas_exp_repmanufacture_info(9)
• mptsas_delete_expander_siblings(9)
• mptsas_expander_delete(9)
• mptsas_send_expander_event(9)
• mptsas_expander_add(9)
• mptsas_probe_expanders(9)
• mptsas_scan_sas_topology(9)
• mptsas_find_phyinfo_by_phys_disk_num(9)
• mptsas_issue_tm(9)
• mptsas_broadcast_primitive_work(9)

Not me listing the entire mptsas extended universe 😭 but fr fr, they're all in the SEE ALSO for a reason — siblings in arms 💀

Okay that's the whole page, you ate that bestie 🌈 this drop came straight out of ./drivers/message/fusion, dated October 2026, filed under the Kernel API Manual as mptsas_del_end_device(9) — iconic, periodt 🎀💖