mptsas_target_reset_queue(9)

Okay bestie, welcome to the mptsas_target_reset_queue(9) page from the Kernel API Manual — yes, we're in kernel API land and it's giving niche but iconic 💅✨

💖 NAME 💖

mptsas_target_reset_queue — queue a target reset 🎯

✨ SYNOPSIS ✨

The signature is literally this, no cap:

void mptsas_target_reset_queue (MPT_ADAPTER *ioc ,
EVENT_DATA_SAS_DEVICE_STATUS_CHANGE *sas_event_data );

🎀 ARGUMENTS 🎀

• ioc — Pointer to MPT_ADAPTER structure 🫶
• sas_event_data — SAS Device Status Change Event data 🌸

🦋 DESCRIPTION 🦋

So here's the vibe: this function receives a request for TARGET_RESET after receiving a firmware event NOT_RESPONDING_EVENT, then it puts the command in the link list and queues it if task_queue is already in use 😭👑

🌈 SEE ALSO 🌈

• Kernel file ./drivers/message/fusion/mptsas.c
• 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_schedule_target_reset(9)
• mptsas_taskmgmt_complete(9)
• mptsas_ioc_reset(9)
• enum device_state(9)
• mptsas_add_end_device(9)
• mptsas_del_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)

This page's source/version footer energy is ./drivers/message/fusion, dated October 2026, and the page handle is mptsas_target_reset_queue(9) — periodt 🎀💜