mpi3mr_update_links(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay so this is a page from the Kernel API Manual, and honestly? it's a whole little glow-up for SAS phys. stay with me bestie 🫢


✨ NAME ✨

mpi3mr_update_links β€” refreshing SAS phy link changes πŸ’…


🌸 SYNOPSIS 🌸

void mpi3mr_update_links (struct mpi3mr_ioc *mrioc , u64
sas_address_parent , u16 handle , u8 phy_number , u8 link_rate , struct
mpi3mr_hba_port *hba_port );

no cap, that's the whole signature β€” void return, six args, we move πŸ’«


πŸŽ€ ARGUMENTS πŸŽ€

  • mrioc β€” your adapter instance reference. it's giving "who am I doing this for" energy 🌈
  • sas_address_parent β€” the SAS address of the parent expander or the host. like, where this phy lives, iykyk πŸ¦‹
  • handle β€” the firmware device handle of the attached device. the firmware's own little ID tag for the device πŸ”₯
  • phy_number β€” the phy number. yes, that's it. that's the whole description πŸ’€
  • link_rate β€” the new link rate. this is the actual change we're refreshing ✨
  • hba_port β€” the HBA port entry πŸ‘‘

⭐ RETURN ⭐

None.

literally nothing comes back. void stays undefeated πŸ’œ


πŸ¦‹ SEE ALSO πŸ¦‹

first up, the kernel file where this lives:

  • Kernel file ./drivers/scsi/mpi3mr/mpi3mr_transport.c πŸ“

and now the full bestie roll-call β€” every single one, no skipping, periodt:

seriously, go read a couple of these. the transport layer is lowkey iconic once you get into it 🧚

that's the whole page, bestie β€” no hidden lore, no extra options, just a clean little phy-refresh function doing its thing πŸ“

mwah πŸ’‹ this one shipped out of ./drivers/scsi/mpi3mr, dated October 2026, and it lives in the manual as mpi3mr_update_links(9) β€” catch you in the next one, love u, bye! πŸŽ€πŸ’–

πŸ“¦ where this page comes from