mpi3mr_expa..._sas_address(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

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

okay so bestie, welcome to the Kernel API Manual, and today's main character is mpi3mr_expander_find_by_sas_address β€” the little function that goes snooping through the mpi3mr driver looking for a specific SAS expander. it's giving "where's my friend" energy but for hardware πŸ”πŸ’–


🌸 NAME 🌸

mpi3mr_expander_find_by_sas_address β€” literally the SAS expander search, no cap πŸ¦‹


✨ SYNOPSIS ✨

struct mpi3mr_sas_node * mpi3mr_expander_find_by_sas_address (struct
mpi3mr_ioc *mrioc , u64 sas_address , struct mpi3mr_hba_port *hba_port
);

like, it hands you back a pointer to a struct mpi3mr_sas_node, or nothing at all. those are the only two moods πŸ’…


πŸŽ€ ARGUMENTS πŸŽ€

  • mrioc β€” the adapter instance reference. it's the controller you're working with, your main connection to the whole mpi3mr situation 🫢
  • sas_address β€” the SAS address of the expander you're hunting for. a u64, so it's a big ol' number, and it's the one thing that actually identifies your target πŸ”₯
  • hba_port β€” the HBA port entry. the port context that goes along with the search 🌈

⭐ RETURN ⭐

a valid SAS expander node... or NULL. that's it. found it, or didn't. iconic binary behaviour honestly πŸ’€

ngl bestie, always check for NULL before you go dereferencing. the function is literally telling you it might come back empty-handed πŸ™ˆ

πŸ¦‹ SEE ALSO πŸ¦‹

the kernel file this lives in: ./drivers/scsi/mpi3mr/mpi3mr_transport.c β€” that's the whole neighborhood, go say hi πŸ‘‹

and now the full friend group, everybody in the mpi3mr transport clique:

like, that's the whole squad, lowkey obsessed with how many of them there are πŸ§šπŸ’œ


and that's the page!! mwah πŸ’‹ this one shipped from ./drivers/scsi/mpi3mr back in October 2026 β€” dated and sourced, slay, periodt πŸŽ€βœ¨πŸ’–

πŸ“¦ where this page comes from