mpt3sas_conf..._volume_wwid(9)
πΈ mpt3sas_config_get_volume_wwid β NAME π
okay so bestie, this is a page from the Kernel API Manual and it's literally about mpt3sas_config_get_volume_wwid β the function that returns the wwid given the volume handle. that's it, that's the whole vibe π
β¨ SYNOPSIS β¨
int mpt3sas_config_get_volume_wwid (struct MPT3SAS_ADAPTER *ioc , u16
volume_handle , u64 *wwid );
like, look at her. three args, one int coming back. iconic signature honestly π«Ά
π¦ ARGUMENTS π¦
iocβ the per adapter object. your whole adapter identity, the main character of this call πvolume_handleβ the volume handle. yes bestie, the handle for the volume. it's giving "pass me the thing so I can find the thing" πwwidβ the volume wwid. this is where the wwid lands, she's a pointer for a reason β¨
πΈ CONTEXT πΈ
sleep.
that's the whole context section. sleep. β meaning this call can sleep, so do not be calling it from somewhere spicy where sleeping is illegal. no cap, respect the context π
β RETURN β
0for success π- non-zero for failure π₯
that's the whole contract, periodt.
π SEE ALSO π
okay so this list is long and I'm obsessed. every single one of these is a real one, don't skip a single name, iykyk:
- 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)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)
that's the whole page bestie, no crumbs left behind π
mwah, this one lives in ./drivers/scsi/mpt3sas, dated October 2026, and it's mpt3sas_conf..._volume_wwid(9) signing off β stay sleepy (in the context sense) and slay your config calls β¨ππ
π¦ 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