ENUM SSAM_REQUEST_FLAGS(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ enum ssam_request_flags β€” Flags for SAM requests ✨

okay bestie, so this is a page from the Kernel API Manual, and it's literally just a little enum that holds the vibe-check rules for SAM requests πŸ’… like, it's short, but it's important, so pay attention 🫢


🌸 SYNOPSIS 🌸

enum ssam_request_flags {
    SSAM_REQUEST_HAS_RESPONSE ,
    SSAM_REQUEST_UNSEQUENCED

};

no cap, that's the whole thing. two flags. two little switches that change how a request gets sent. iconic behavior honestly πŸŽ€


🌈 Constants 🌈

  • SSAM_REQUEST_HAS_RESPONSE β€” this one's saying "bestie, i expect a reply πŸ’Œ". if it's not set, the request gets directly completed right after its underlying packet has been transmitted β€” like, done, bye, no waiting around. but if it is set, the request transport system waits for a response to the request. it's giving "read receipt on" energy πŸ‘€
  • SSAM_REQUEST_UNSEQUENCED β€” this one means the request should be transmitted via an unsequenced packet ⚑ and here's the tea: if this is set, the request must not have a response. so this flag and the SSAM_REQUEST_HAS_RESPONSE flag are mutually exclusive β€” pick one, you cannot have both, that's the rules fr fr πŸ™ˆ
ok so quick recap because i love you: HAS_RESPONSE = "i want a reply", UNSEQUENCED = "sent unsequenced, and therefore absolutely no reply allowed". they do NOT coexist. periodt πŸ’€

πŸ¦‹ SEE ALSO πŸ¦‹

like i said β€” a LOT of friends. go read them, they're all slay, i promise πŸ§šβ€β™€οΈ


aaaand that's the page!! shipped from ./include/linux/surface_aggregator/controller.h, stamped October 2026, living in the Kernel API Manual πŸ’– mwah, go write some kernel code bestie, you got this β­πŸ‘‘

πŸ“¦ where this page comes from