mpt3sas_tran...expander_phy(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… mpt3sas_transport_add_expander_phy β€” a.k.a. the mpt3sas_tran...expander_phy(9) glow-up ✨

okay so bestie, welcome to the Kernel API Manual πŸŽ€ β€” this one is a function page, and yes the header is literally truncated with ... in the middle which is giving "my mom named the file". we move.


🌸 NAME 🌸

mpt3sas_transport_add_expander_phy β€” report expander phy to transport πŸ¦‹

like, it introduces an expander phy to the transport layer. that's the whole vibe. no cap.


✨ SYNOPSIS ✨

int mpt3sas_transport_add_expander_phy (struct MPT3SAS_ADAPTER *ioc ,
struct _sas_phy *mpt3sas_phy , Mpi2ExpanderPage1_t expander_pg1 , struct
device *parent_dev );

it returns an int, it takes four things, and it's literally right there for you to copy πŸ’–


🫢 ARGUMENTS 🫢

  • ioc β€” the per adapter object 🌈 like, the whole adapter's main character energy right here.
  • mpt3sas_phy β€” the mpt3sas per phy object πŸ’œ one specific phy, being all individual about it.
  • expander_pg1 β€” expander page 1 πŸ“„ yep. that page. page one. iconic.
  • parent_dev β€” the parent device class object πŸ‘‘ the device that's basically the parent in this whole situation, fr fr.

πŸ’€ RETURN πŸ’€

0 for success, non-zero for failure. that's it, that's the whole story πŸ“

careful bestie β€” non-zero is failure, so don't go treating any random number like it's a win 😭

πŸ”₯ SEE ALSO πŸ”₯

the full squad, in order, no one left behind 🫑

like, that's a whole friend group right there 🌈 go read them too, iykyk πŸ’…


and that's the page, bestie 🧚 this little beauty lives over in ./drivers/scsi/mpt3sas, dated October 2026 β€” yes, the future said hi πŸ‘‹ stay slay, ship it, and don't forget the 0 means success πŸ’–βœ¨

πŸ“¦ where this page comes from