mpt3sas_raid...nd_by_handle(9)

📦 version 7.3.1, in nixpkgs unstable

💅 mpt3sas_raid_device_find_by_handle(9) 💅

okay so bestie, welcome to the Kernel API Manual ✨ — this one's a little lookup function from the mpt3sas driver and it's honestly so simple it's giving main character energy in its minimalism. Let's get into it 🫶

🌸 NAME 🌸

mpt3sas_raid_device_find_by_handle — the raid device search. that's it, that's the whole vibe. you hand it a handle, it hands you a raid device. slay 🔥

🎀 SYNOPSIS 🎀

struct _raid_device * mpt3sas_raid_device_find_by_handle (struct
MPT3SAS_ADAPTER *ioc , u16 handle );

🦋 ARGUMENTS 🦋

  • ioc — the per adapter object, aka the whole controller's whole personality 💜
  • handle — the sas device handle (assigned by firmware, so like, not your call, the firmware picked it, respect it 👑)

⚠️ CONTEXT ⚠️

the calling function should acquire ioc->raid_device_lock — no cap, this is not optional, bestie 😭 lock it before you call it or things get messy.

💖 DESCRIPTION 💖

so what does it actually do? it searches for the raid_device based on the handle, then returns the raid_device object. literally that's it. a little find-and-return. lowkey iconic for how unbothered it is 💅

🌈 SEE ALSO 🌈

okay this is the part where it gets unhinged — the cross-reference list is long long. like, main-character-of-the-whole-source-file long. here's every single one, preserved in all its glory ✨

and that's the whole page, bestie 🧚 this little cutie lives in ./drivers/scsi/mpt3sas, dated October 2026, and the manual itself answers to the name mpt3sas_raid...nd_by_handle(9) — yes the header truncates it, no we don't know why, and honestly? we're not gonna ask 💀 bye bye, go lock that raid_device_lock before you call anything 🎀

📦 where this page comes from