mpt3sas_con...cturing_pg11(9)
π mpt3sas_config_set_manufacturing_pg11 β bestie, we're setting Manufacturing Page 11 β¨
Okay so this is a page from the Kernel API Manual, and the function's full name is mpt3sas_config_set_manufacturing_pg11 (the header up top is just that name gettin' a little truncated: mpt3sas_con...cturing_pg11(9) β she's long, she's iconic, she got cut off π).
β¨ NAME β¨
mpt3sas_config_set_manufacturing_pg11 β set manufacturing page 11. That's the whole vibe, no cap.
π¦ SYNOPSIS π¦
int mpt3sas_config_set_manufacturing_pg11 (struct MPT3SAS_ADAPTER *ioc ,
Mpi2ConfigReply_t *mpi_reply , struct Mpi2ManufacturingPage11_t
*config_page );
It returns an int, and it takes three little args. Slay. π
πΈ ARGUMENTS πΈ
iocβ the per adapter object. Like, your adapter's whole personality in one struct.mpi_replyβ the reply mf payload that the firmware hands back to you. Firmware said "here's what I think" and this is where she says it π₯config_pageβ the actual contents of the config page. This is the stuff you're sending in.
π CONTEXT π
sleep.
Yeah. That's it. That's the whole section. She sleeps π΄ β meaning you can sleep in this context, so don't go callin' her from somewhere spicy where sleepin' is illegal. You've been warned, bestie π«Ά
π RETURN π
0for success π- non-zero for failure π
That's the classic zero-is-good, everything-else-is-a-problem situation. Fr fr.
π SEE ALSO π
Grab a snack, because this list is long and honestly she ate:
- 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_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)_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)
Every single one of them, present and accounted for. Periodt. π
So yeah β that's the whole page. Set page 11, respect the sleep context, check your return value, and go read about the fifty-eleven sibling functions above. Iykyk π
π and that's a wrap, bestie! This lil' cutie comes from the source path ./drivers/scsi/mpt3sas, dated October 2026, and she lives in the Kernel API Manual. Mwah! πβ¨π¦
π¦ 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