SCU_GET_FRAME_INDEX(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… SCU_GET_FRAME_INDEX(9) β€” like, the Kernel API Manual edition, bestie ✨

okay so real talk, this is a page straight out of the Kernel API Manual and it's giving "tiny macro, huge responsibility" energy. buckle up πŸŽ€


✨ NAME ✨

SCU_GET_FRAME_INDEX β€” and honestly the official NAME line doesn't even give us a description after the dash, so like... that's the whole name section. no cap. we move πŸ’€


🌸 SYNOPSIS 🌸

SCU_GET_FRAME_INDEX (completion_code );

that's it. that's the whole call. one argument, one macro, zero drama (mostly) πŸ¦‹


πŸŽ€ ARGUMENTS πŸŽ€

  • completion_code β€” sooooo the original manpage literally says "-- undescribed --" for this one 😭 like the docs team just left it blank and dipped. bestie i'm not gonna invent a description for you because that would be lying and we don't do that here. it's the completion code. that's all we've got. iykyk πŸ™ˆ

πŸ’œ DESCRIPTION πŸ’œ

okay so here's the tea: this macro returns a normalized frame index from an unsolicited frame completion. that's the whole vibe. it takes your completion and hands you back a tidy, normalized frame index, periodt ✨


πŸ‘‘ SEE ALSO πŸ‘‘

first up, the source file where all this lives β€” go read it, it's iconic:

Kernel file ./drivers/scsi/isci/scu_completion_codes.h

and now the whole friend group of related macros, fr fr, all of them, no skipping:


ok that's the whole page bestie, it's a short one but she ate πŸ“

mwah πŸ’‹ this has been your girl signing off β€” page sourced from ./drivers/scsi/isci, dated October 2026, and honestly? iconic behavior. go get that frame index πŸ‘‘βœ¨

πŸ“¦ where this page comes from