SCU_GET_COMPLETION_PEG(9)

📦 version 7.3.1, in nixpkgs unstable

🌸 SCU_GET_COMPLETION_PEG(9) 🌸

okay bestie, welcome to the Kernel API Manual — yes, that Kernel API Manual, the one with the lore 💅. This page is all about a macro with a name so long it's giving "my coffee order" energy: SCU_GET_COMPLETION_PEG. It lives in the SCSI/isci corner of the kernel and it's lowkey iconic. Let's get into it 🫶

✨ SYNOPSIS ✨

SCU_GET_COMPLETION_PEG (completion_code );

that's it. one argument. she's simple, she's clean, she slays 💖

🎀 ARGUMENTS 🎀

  • completion_code — and honestly? the original docs just say -- undescribed -- 😭😭 which is the most "we'll fill this in later" vibe ever. not me leaving a TODO in production fr fr. so yeah, that's the whole description we've got: undescribed. no cap. 💀

🔥 DESCRIPTION 🔥

okay so here's the actually useful part: this macro returns the Protocol Engine Group from the completion code. that's it, that's the tea ☕. you hand it a completion code, it hands you back the Protocol Engine Group. main character energy, minimal dialogue, in and out 🌈

bestie note: the argument is literally listed as undescribed above, so don't go inventing extra behaviour in your head — this page tells you what it says and nothing more 🙈

👑 SEE ALSO 👑

the whole squad, and yes they all have names that start with SCU_ because the naming committee had a vision 💅

like, that's thirteen references plus the header file. she has a friend group, okay, she's not lonely 🌸

and that's the whole page, bestie!! go forth and get those completion PEGs 💜

💖 sign-off szn: this little beauty ships from ./drivers/scsi/isci, dated October 2026 — periodt. 🎀
📦 where this page comes from