scsi_is_sas_phy(9)

📦 version 7.3.1, in nixpkgs unstable

✨ scsi_is_sas_phy ✨

okay so real talk bestie, this is a page straight out of the Kernel API Manual and it's genuinely a lil one-function wonder 🎀 — it does exactly one thing and it does it iconically.

💅 NAME

scsi_is_sas_phy — check if a struct device represents a SAS PHY

like yes, that's the whole gig. it's a vibe check for devices ✨

🦋 SYNOPSIS

int scsi_is_sas_phy (const struct device *dev );

🌸 ARGUMENTS

  • dev — the device you wanna check 👀 that's it, that's the whole arg list, she's low maintenance

🔥 RETURN

  • 1 if the device represents a SAS PHY 💖
  • 0 else 🙈

so basically a yes/no, no in-between, no "it depends", no drama. she ate and left no crumbs 🫶

👑 SEE ALSO

okay this is the part where it gets highkey unhinged, because there are like a zillion friends in the group chat 💀 first up, the kernel file this all lives in:

./drivers/scsi/scsi_transport_sas.c

and then the whole squad, in order, no cap:

like?? that's the entire extended friend group and every single one of them gets a name drop 💅 no one left on read.

ngl, if you came here looking for options or flags or env vars — there are literally none. this page is one function, one argument, one return value, and thirty-one see-also besties. periodt ✨

🌈 and that's the whole page!! mwah 💖 this lil beauty lives in ./drivers/scsi and the manual is dated October 2026 — so yeah, she's from the future, main character energy fr fr 🧚‍♀️🦋⭐

📦 where this page comes from