SCU_GET_COMPLETION_PORT(9)

📦 version 7.3.1, in nixpkgs unstable

💅 SCU_GET_COMPLETION_PORT — the kernel API manual, bestie edition ✨

Okay so listen, we're looking at SCU_GET_COMPLETION_PORT from the SCU_GET_COMPLETION_PORT(9) man page, a whole kernel API situation, and honestly? It's a little one. A little baby macro. But we're gonna give it the main character energy it deserves 🎀

🌸 NAME 🌸

SCU_GET_COMPLETION_PORT — and yes the original description line is literally empty, so no cap, that's all the NAME section gives us 😭 the macro name and vibes.

✨ SYNOPSIS ✨

SCU_GET_COMPLETION_PORT (completion_code );

That's it. One argument, one call. She's lowkey simple like that 🦋

🫶 ARGUMENTS 🫶

  • completion_code — the original page says, and I quote-ish, "-- undescribed --" 💀 not a single word of description. Iconic behaviour honestly. So like… it's the completion code you pass in. That's all we know. We respect the mystery 🙈

💜 DESCRIPTION 💜

This macro returns the logical port index from the completion code. That's the whole thing! That's the plot! You hand it a completion code, it hands you back a port index, and it does it logically, which is the best way to do things honestly 🔥

No options, no env vars, no exit statuses, no bugs listed — she's a one-liner through and through 👑

Heads up bestie: this is literally all the original page says about behaviour, so don't go reading more into it than that. 💅

🌈 SEE ALSO 🌈

The kernel file that lives with all this:

  • ./drivers/scsi/isci/scu_completion_codes.h

And the full squad of related macros, all of them, no skipping, fr fr:

And that's the page, bestie! 🧚 This little gem comes courtesy of ./drivers/scsi/isci, dated October 2026 — so like, freshly stamped and ready to slay. Go forth and get those completion ports 💖✨

📦 where this page comes from