mpt3sas_con..._trigger_pg1(9)
π mpt3sas_con..._trigger_pg1(9) π
okay so this is a page straight out of the Kernel API Manual, and yes the page name is literally truncated with ellipsis in the header (mpt3sas_con..._trigger_pg1(9)) β that's not me being lazy, that's just how it's printed, bestie.
πΈ NAME πΈ
mpt3sas_config_get_driver_trigger_pg1 β the girl whose whole job is to obtain driver trigger page 1. that's it. that's the mission. π
β¨ SYNOPSIS β¨
int mpt3sas_config_get_driver_trigger_pg1 (struct MPT3SAS_ADAPTER *ioc ,
Mpi2ConfigReply_t *mpi_reply , Mpi26DriverTriggerPage1_t *config_page );
like, it returns an int, it takes three args, it's giving "small function, big responsibilities" energy. π₯
π ARGUMENTS π
iocβ the per adapter object. yes, the whole adapter. she's the main character and everything hangs off her πmpi_replyβ the reply mf payload returned from firmware. firmware said something back and this is where it lives π«Άconfig_pageβ contents of the config page. the actual goods, the payload, the reason we're all here β¨
π¦ CONTEXT π¦
sleep.
that's the whole thing. lowercase. period. she naps. π΄ do not come for her in atomic context, okay? she sleeps and she means it.
π DESCRIPTION π
Returns 0 for success, non-zero for failure. no cap, that's the entire description β binary queen behavior, we love a straightforward icon π
β SEE ALSO β
grab a snack, this list is long β but every single one of these is invited to the group chat π§:
- Kernel file
./drivers/scsi/mpt3sas/mpt3sas_config.c struct config_request(9)_config_display_some_debug(9)_config_alloc_config_dma_memory(9)_config_free_config_dma_memory(9)mpt3sas_config_done(9)_config_request(9)mpt3sas_config_get_manufacturing_pg0(9)mpt3sas_config_get_manufacturing_pg1(9)mpt3sas_config_get_manufacturing_pg10(9)mpt3sas_config_get_manufacturing_pg11(9)mpt3sas_config_set_manufacturing_pg11(9)mpt3sas_config_get_bios_pg2(9)mpt3sas_config_get_bios_pg3(9)mpt3sas_config_set_bios_pg4(9)mpt3sas_config_get_bios_pg4(9)mpt3sas_config_get_iounit_pg0(9)mpt3sas_config_get_iounit_pg1(9)mpt3sas_config_set_iounit_pg1(9)mpt3sas_config_get_iounit_pg3(9)mpt3sas_config_get_iounit_pg7(9)mpt3sas_config_get_iounit_pg8(9)mpt3sas_config_get_ioc_pg8(9)mpt3sas_config_get_ioc_pg1(9)mpt3sas_config_set_ioc_pg1(9)mpt3sas_config_get_sas_device_pg0(9)mpt3sas_config_get_pcie_device_pg0(9)mpt3sas_config_get_pcie_iounit_pg1(9)mpt3sas_config_get_pcie_device_pg2(9)mpt3sas_config_get_number_hba_phys(9)mpt3sas_config_get_sas_iounit_pg0(9)mpt3sas_config_get_sas_iounit_pg1(9)mpt3sas_config_set_sas_iounit_pg1(9)mpt3sas_config_get_expander_pg0(9)mpt3sas_config_get_expander_pg1(9)mpt3sas_config_get_enclosure_pg0(9)mpt3sas_config_get_phy_pg0(9)mpt3sas_config_get_phy_pg1(9)mpt3sas_config_get_raid_volume_pg1(9)mpt3sas_config_get_number_pds(9)mpt3sas_config_get_raid_volume_pg0(9)mpt3sas_config_get_phys_disk_pg0(9)mpt3sas_config_get_driver_trigger_pg0(9)_config_set_driver_trigger_pg0(9)mpt3sas_config_update_driver_trigger_pg0(9)_config_set_driver_trigger_pg1(9)mpt3sas_config_update_driver_trigger_pg1(9)mpt3sas_config_get_driver_trigger_pg2(9)_config_set_driver_trigger_pg2(9)mpt3sas_config_update_driver_trigger_pg2(9)mpt3sas_config_get_driver_trigger_pg3(9)_config_set_driver_trigger_pg3(9)mpt3sas_config_update_driver_trigger_pg3(9)mpt3sas_config_get_driver_trigger_pg4(9)_config_set_driver_trigger_pg4(9)mpt3sas_config_update_driver_trigger_pg4(9)mpt3sas_config_get_volume_handle(9)mpt3sas_config_get_volume_wwid(9)
the way that every pg0 through pg11 sibling showed up to support herβ¦ a family. ππ
lowkey obsessed with how a function that just grabs page 1 has this many friends. networking icon fr fr. π
okay that's the whole page!! this one lives over in ./drivers/scsi/mpt3sas, and it's dated October 2026 β so yeah, she's from the future, we stan a time traveler π°οΈβ¨ bye bestie, go read the next manpage ππ¦π
π¦ 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