mpi3mr_cfg_get_sas_phy_pg1(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… mpi3mr_cfg_get_sas_phy_pg1(9) β€” Kernel API Manual ✨

okay so bestie, welcome to the Kernel API Manual entry for mpi3mr_cfg_get_sas_phy_pg1(9) β€” yes that's a real function name and yes we're gonna read it together 🫢


🌸 NAME 🌸

mpi3mr_cfg_get_sas_phy_pg1 β€” read the current SAS Phy page1, no cap πŸ’–


πŸŽ€ SYNOPSIS πŸŽ€

int mpi3mr_cfg_get_sas_phy_pg1 (struct mpi3mr_ioc *mrioc , u16
*ioc_status , struct mpi3_sas_phy_page1 *phy_pg1 , u16 pg_sz , u32 form
, u32 form_spec );

like, that's the whole signature, copy it exactly, iykyk ✨


πŸ¦‹ ARGUMENTS πŸ¦‹

  • mrioc β€” your adapter instance reference, the main character of this whole function ngl
  • ioc_status β€” a pointer where we return the ioc status 🫢
  • phy_pg1 β€” pointer to return the SAS Phy page 1 into, that's the whole vibe
  • pg_sz β€” the size of the memory you allocated to the page pointer, pls don't lie about this one πŸ™ˆ
  • form β€” the form used for addressing the page
  • form_spec β€” form-specific info, like the phy number, the little details that matter πŸ’…

πŸ‘‘ DESCRIPTION πŸ‘‘

So this is the handler for a config page read β€” specifically for one specific SAS Phy page1. Iconic, honestly.

The ioc_status ends up holding the controller's returned ioc_status. And here's the important part, bestie, listen up: this routine does not check ioc_status to decide whether the page read succeeded or not. That's literally the caller's job. It's giving "I did my part, you do yours" energy 😭

🚨 fr fr, do not assume success just because the function came back β€” check that ioc_status yourself, it's on you πŸ’€

⭐ RETURN ⭐

0 on success, non-zero on failure. That's it, that's the whole vibe check 🌈


πŸ”₯ SEE ALSO πŸ”₯

All the sibling functions living in the kernel file ./drivers/scsi/mpi3mr/mpi3mr_fw.c β€” go say hi to the whole fam πŸ’œ

(yes mpimr_initialize_reply_sbuf_queues(9) really is spelled like that, not me, don't come for me πŸ™ˆ)


πŸ’« sign-off bestie πŸ’«

This lil page lives in ./drivers/scsi/mpi3mr, dated October 2026, and it's the mpi3mr_cfg_get_sas_phy_pg1(9) manual page in the Kernel API Manual. Go read your ioc_status, hydrate, and stan responsibly πŸ’…βœ¨πŸŽ€

πŸ“¦ where this page comes from