mpi3mr_cfg_get_driver_pg1(9)

📦 version 7.3.1, in nixpkgs unstable

💅 mpi3mr_cfg_get_driver_pg1 — like, the whole entire vibe 💅

okay so bestie, welcome to the Kernel API Manual entry for mpi3mr_cfg_get_driver_pg1. yes that's a mouthful, no i will not be shortening it, we respect the function's full government name here 🫶

✨ NAME ✨

mpi3mr_cfg_get_driver_pg1 — read the current Driver page1. that's it. that's the whole job. iconic, honestly 🎀

🌸 SYNOPSIS 🌸

int mpi3mr_cfg_get_driver_pg1 (struct mpi3mr_ioc *mrioc , struct
mpi3_driver_page1 *driver_pg1 , u16 pg_sz );

look at her. three params, one int coming back at you. main character energy fr fr ⭐

🦋 ARGUMENTS 🦋

  • mrioc — the adapter instance reference. like, which adapter are we talking to, bestie? this is how the routine knows 💜
  • driver_pg1 — a pointer to where the Driver page 1 is gonna get returned. this is the lil landing pad for the goods 🎀
  • pg_sz — the size of the memory that's been allocated to that page pointer. pls get this right, it's literally the size of your buffer, no cap 🙈

🔥 DESCRIPTION 🔥

so this is the handler for the config page read for the Driver page1 — the one that goes and fetches it for you 🧚

and here's the cute part: the routine checks ioc_status to decide whether the page read was a success or... not a success 😭. that's the whole vibe check. status says yes → slay. status says no → we go handle that.

⭐ RETURN ⭐

0 on success, non-zero on failure. classic. binary. no in-between, and that's on periodt 💅

🌈 SEE ALSO 🌈

okay this list is LONG long, like the function has so many friends, it's giving popular girl at the function 👑. live in the kernel file ./drivers/scsi/mpi3mr/mpi3mr_fw.c and go meet the whole squad:

(i know. screenshot it, memorize it, whatever you gotta do 💀)

and that's the page, bestie 🫶 shoutout to the source over in ./drivers/scsi/mpi3mr, dated October 2026, living under the Kernel API Manual name — go read her siblings, they're all lowkey obsessed with each other 💖✨

📦 where this page comes from