mpt_raid_phys_disk_pg0(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ NAME πŸŽ€

okay bestie, this is the mpt_raid_phys_disk_pg0(9) page from the Kernel API Manual, and the main character is mpt_raid_phys_disk_pg0 β€” its whole iconic job is literally: returns phys disk page zero. no cap, that's the vibe. πŸ’…

✨ SYNOPSIS ✨

the signature is giving β€œtrust me, I know what I'm doing”:

int mpt_raid_phys_disk_pg0 (MPT_ADAPTER *ioc , u8 phys_disk_num ,
       RaidPhysDiskPage0_t *phys_disk );

πŸ’… ARGUMENTS πŸ’…

  • ioc β€” pointer to a Adapter Structure. lowkey the adapter context, bestie. 🫢
  • phys_disk_num β€” io unit unique phys disk num generated by the ioc. yes, β€œio unit unique” exactly β€” we don't make the rules. ✨
  • phys_disk β€” the requested payload data returned. so this is where the good stuff lands. πŸŽ€

🌈 RETURN 🌈

  • 0 β€” on success. we love a clean return, periodt. πŸ’–
  • -EFAULT β€” if the read of the config page header fails, or if the data pointer is not NULL. that's the exact caveat, bestie. 😭
  • -ENOMEM β€” if pci_alloc failed. sad, but at least the error code is honest. πŸ’€

πŸ¦‹ SEE ALSO πŸ¦‹

the kernel file is ./drivers/message/fusion/mptbase.c, and the whole friend group is:


that's the whole page, bestie πŸ’… β€” source/version: ./drivers/message/fusion, dated October 2026. mwah πŸ’‹πŸ’–

πŸ“¦ where this page comes from