_config_set_..._trigger_pg2(9)
π _config_set_..._trigger_pg2(9) π
okay so bestie, welcome to the Kernel API Manual β¨ you're literally about to learn how to write driver trigger page 2, and honestly? iconic behavior π
β¨ NAME β¨
_config_set_driver_trigger_pg2 β writes driver trigger page 2, no cap π
πΈ SYNOPSIS πΈ
int _config_set_driver_trigger_pg2 (struct MPT3SAS_ADAPTER *ioc ,
Mpi2ConfigReply_t *mpi_reply , Mpi26DriverTriggerPage2_t *config_page );
like, that's the whole signature, copy it exactly please, we do not freestyle here π«Ά
π¦ ARGUMENTS π¦
iocβ per adapter object. it's the adapter's whole little world, okay? every adapter gets its own π«mpi_replyβ reply mf payload returned from firmware. the firmware literally texts you back and this is the message π±config_pageβ contents of the config page. the actual page you're setting, right there in your hands π
π§ CONTEXT π§
sleep.
that's it. that's the context. you can sleep π΄ she's a sleepy one, so don't go calling her from somewhere spicy like an interrupt context, bestie, that's giving chaos π
π DESCRIPTION π
Returns 0 for success, non-zero for failure. periodt. that's the entire personality of the return value π
no like genuinely, that's it β 0 and you slayed, non-zero and something went sideways π
π SEE ALSO π
the whole friend group, fr fr β go say hi to all of them π
Kernel file ./drivers/scsi/mpt3sas/mpt3sas_config.cstruct 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)mpt3sas_config_get_driver_trigger_pg1(9)_config_set_driver_trigger_pg1(9)mpt3sas_config_update_driver_trigger_pg1(9)mpt3sas_config_get_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)
and that's the whole page, bestie π«Ά you ate, no crumbs π
this masterpiece lives in ./drivers/scsi/mpt3sas, the version vibe is October 2026, and it's filed under _config_set_..._trigger_pg2(9) β go forth and write that page 2, queen πβ¨
π¦ 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