sas_phy_free(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ sas_phy_free ✨

okay so this is a page straight out of the Kernel API Manual β€” it's sas_phy_free(9), bestie, and it's honestly so short and so real. let's get into it πŸ’…


🌸 NAME 🌸

sas_phy_free β€” free a SAS PHY. that's it. that's the whole vibe. πŸ¦‹


✨ SYNOPSIS ✨

void sas_phy_free (struct sas_phy *phy );

like, no return value, no drama, it just does the thing and dips. periodt.


πŸŽ€ ARGUMENTS πŸŽ€

  • phy β€” the SAS PHY you wanna free. the one. the main character. hand it over and it's gone πŸ’¨

πŸ’– DESCRIPTION πŸ’–

Frees the specified SAS PHY. literally that's it, that's the function. no cap. 🫢


πŸ”₯ NOTE πŸ”₯

okay this is the important part, so listen up bestie πŸ™ˆ

This function must only be called on a PHY that has not successfully been added using sas_phy_add.

like, if you already added it with sas_phy_add and it worked? do not come here. that's not this function's moment. this is a very specific lane, and we stay in it. respect the rules or the kernel will disrespect you back πŸ˜­πŸ’€


🌈 SEE ALSO 🌈

the whole friend group, no one left out, all of them tagged with (9) because we're consistent:

and if you're wondering where all this lives β€” it's the kernel file ./drivers/scsi/scsi_transport_sas.c. note it, screenshot it, put it on your fridge πŸ§šβ€β™€οΈ


kisses and goodbyes β€” this page comes to you from ./drivers/scsi, dated October 2026, and it's filed under sas_phy_free(9) forever and ever. slay πŸ’œ

πŸ“¦ where this page comes from