SCU_GET_PRO...ENGINE_INDEX(9)

💅 SCU_GET_PRO...ENGINE_INDEX(9) 💅

okay so bestie, welcome to the Kernel API Manual — yes that's the whole manual name, we're in the kernel docs now, put your hair up 🎀

---

✨ NAME ✨

SCU_GET_PROTOCOL_ENGINE_INDEX — and honestly? the description field is just... empty. nothing. void. the manpage said - and left it at that 🙈 so we're not gonna invent lore, we're just gonna vibe with the mystery.

---

🌸 SYNOPSIS 🌸

SCU_GET_PROTOCOL_ENGINE_INDEX (completion_code );

that's it. that's the whole call. one single argument, in and out, iconic behavior fr fr ✨

---

🦋 ARGUMENTS 🦋

• completion_code — literally marked "-- undescribed --" in the source. no cap, that's what it says. the docs did NOT come through for us here 😭 so we're telling you exactly as much as we were told, nothing more, periodt.

---

💖 DESCRIPTION 💖

so what does it do? this macro returns the PE index from the completion code. that's the entire bit. short, sweet, main character energy 👑

not me being unable to embellish this one — there is genuinely nothing else documented, so please don't come for me, I am only relaying the facts 🫶

---

🔥 SEE ALSO 🔥

• Kernel file ./drivers/scsi/isci/scu_completion_codes.h — go read the source bestie, it's giving primary evidence 💀
• SCU_COMPLETION_TYPE(9)
• SCU_GET_COMPLETION_TYPE(9)
• SCU_GET_COMPLETION_STATUS(9)
• SCU_GET_COMPLETION_TL_STATUS(9)
• SCU_MAKE_COMPLETION_STATUS(9)
• SCU_NORMALIZE_COMPLETION_STATUS(9)
• SCU_GET_COMPLETION_SDMA_STATUS(9)
• SCU_GET_COMPLETION_PEG(9)
• SCU_GET_COMPLETION_PORT(9)
• SCU_GET_COMPLETION_INDEX(9)
• SCU_GET_FRAME_INDEX(9)
• SCU_GET_FRAME_ERROR(9)

like a whole little completion-code friend group, and our macro is part of it 🌈

---

🧚 sign-off 🧚

this one came out of ./drivers/scsi/isci and it's dated October 2026 — yes, the future, we're in our time-travel era ⭐ anyway slay, go forth and index your PEs, ily, bye 💜