akcipher_re...set_callback(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– akcipher_re...set_callback(9) πŸ’–

okay so this is from the Kernel API Manual, and the page is literally called akcipher_re...set_callback (yes the name is truncated with dots, that's just how it is bestie, don't come for it πŸ’…). Buckle up, we're setting callbacks on async akcipher requests and it's gonna be iconic.


✨ NAME ✨

akcipher_request_set_callback β€” sets an asynchronous callback. that's it. that's the whole vibe. πŸŽ€


🌸 SYNOPSIS 🌸

void akcipher_request_set_callback (struct akcipher_request *req , u32
flgs , crypto_completion_t cmpl , void *data );

like, look at her. four params, returns void, zero drama. πŸ¦‹


🧚 ARGUMENTS 🧚

  • req β€” the request that the callback will be set for. this is the main character of the operation, the one we're attaching the callback to. πŸ‘‘
  • flgs β€” flags, and they specify for instance if the operation may backlog. yes it's spelled flgs, no we're not fixing it, it's canon. πŸ’€
  • cmpl β€” the callback which will be called. the whole point of the function honestly, the cmpl is the moment. πŸ”₯
  • data β€” private data used by the caller. your little stash, your personal lore, passed through for you. πŸ™ˆ

πŸ’œ DESCRIPTION πŸ’œ

so basically: the callback will be called when an asynchronous operation on a given request is finished. that's the tea. you hand over your cmpl and your data, and when the async op wraps up on that req, your callback gets the glow-up and runs. no cap, that's the entire behavior described here. ⭐


🫢 SEE ALSO 🫢

like a whole friend group of crypto functions, go say hi to all of them, iykyk πŸ’–


and that's the page!! 🌈 this little number lives over in ./include/crypto and it's dated October 2026 β€” yes, 2026, she's from the future, we don't question it. periodt. πŸ’…βœ¨

πŸ“¦ where this page comes from