mpi3mr_add_expander_phy(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ NAME ✨

okay bestie, meet mpi3mr_add_expander_phy(9) β€” it's from the Kernel API Manual, and its whole vibe is literally report expander phy to transport. no cap, that's the name-and-description combo, and yes the spelling is exactly phy, lowercase, we respect it. πŸ¦‹


🌸 SYNOPSIS 🌸

here's the signature, copied exactly because bestie we do not mess with C types:

int mpi3mr_add_expander_phy (struct mpi3mr_ioc *mrioc , struct
       mpi3mr_sas_phy *mr_sas_phy , struct mpi3_sas_expander_page1 expander_pg1
       , struct device *parent_dev );

the return type is int, and the function name and all the argument types are exactly as above. iconic. ✨


πŸ’… ARGUMENTS πŸ’…

bestie, there are four arguments, and they are all right here:

  • mrioc β€” Adapter instance reference. the adapter's whole reference vibe. 🫢
  • mr_sas_phy β€” Internal Phy object. yes, capital P in Phy, we keep it exactly. πŸ’–
  • expander_pg1 β€” SAS Expander page 1. that's the SAS Expander page 1 data, periodt.
  • parent_dev β€” Parent device class object. the parent-device class object, right there in the signature. 🌈

πŸ”₯ RETURN πŸ”₯

  • 0 for success.
  • non-zero for failure.

that's literally the whole return vibe: 0 for success, non-zero for failure. 😭


πŸŽ€ SEE ALSO πŸŽ€

first up, the kernel file: ./drivers/scsi/mpi3mr/mpi3mr_transport.c.

then the huge friend group, all of these exact references:


and that's the page, bestie β€” source/version is ./drivers/scsi/mpi3mr, dated October 2026, signed off with maximum sparkle and zero missing references. πŸ’–πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from