__mpi3mr_exp...nd_by_handle(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

okay bestie, this page is __mpi3mr_exp...nd_by_handle(9) from the Kernel API Manual, and the function is __mpi3mr_expander_find_by_handle β€” literally β€œexpander search by handle.” Periodt. ✨

🌸 SYNOPSIS 🌸

struct mpi3mr_sas_node * __mpi3mr_expander_find_by_handle (struct
mpi3mr_ioc *mrioc , u16 handle );

πŸŽ€ ARGUMENTS πŸŽ€

  • mrioc β€” the adapter instance reference, aka the main character adapter pointer πŸ’…
  • handle β€” the firmware device handle of the expander; this is the handle we’re searching with, no cap.

πŸ¦‹ CONTEXT πŸ¦‹

Context check, bestie: the caller should acquire sas_node_lock 🫢

✨ DESCRIPTION ✨

So here’s the serve: this searches for the expander device based on handle, then returns the sas_node object. That’s the move. πŸ’–

πŸ”₯ RETURN πŸ”₯

Return vibe check: an expander sas_node object reference, or NULL. That’s it, that’s the whole answer. 🌈

πŸ‘€ SEE ALSO πŸ‘€

Kernel file: ./drivers/scsi/mpi3mr/mpi3mr_transport.c β€” iconic source-file energy. πŸŽ€

The whole ref squad:


Final sign-off, bestie: source/version ./drivers/scsi/mpi3mr, date October 2026, page __mpi3mr_exp...nd_by_handle(9) πŸ’–πŸŽ€

πŸ“¦ where this page comes from