mpt3sas_con..._trigger_pg2(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 NAME 🌸

Okay bestie, welcome to mpt3sas_con..._trigger_pg2(9) from the Kernel API Manual β€” the function is mpt3sas_config_get_driver_trigger_pg2, and its whole job is to obtain driver trigger page 2. πŸ’…βœ¨

✨ SYNOPSIS ✨

int mpt3sas_config_get_driver_trigger_pg2 (struct MPT3SAS_ADAPTER *ioc , Mpi2ConfigReply_t *mpi_reply , Mpi26DriverTriggerPage2_t *config_page );

πŸŽ€ ARGUMENTS πŸŽ€

  • ioc β€” per adapter object. Like, the adapter's main-character handle. 🫢
  • mpi_reply β€” reply mf payload returned from firmware. The firmware's little message back. πŸ’Œ
  • config_page β€” contents of the config page. The page itself, no cap. πŸ“„

πŸ’€ CONTEXT πŸ’€

sleep. 😴 That's the context. That's the whole mood.

πŸ¦‹ DESCRIPTION πŸ¦‹

Returns 0 for success, non-zero for failure. So 0 is the slay, non-zero is the "welp" 😭 β€” but that's literally the return contract.

πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./drivers/scsi/mpt3sas/mpt3sas_config.c struct config_request(9) β€” and here's the whole bestie list:


Sign-off: source/version ./drivers/scsi/mpt3sas Β· date October 2026 Β· page mpt3sas_con..._trigger_pg2(9). Byeee bestie, go get that driver trigger page 2! πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from