finish_req(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… finish_req(9) β€” Kernel API Manual πŸŽ€

okay so bestie, welcome to finish_req, straight out of the Kernel API Manual. this one is lowkey short but it's iconic, trust. ✨


🌸 NAME 🌸

finish_req β€” the little function that's used to invoke the complete callback from the requester when a request has been handled asynchronously. she's the "ok we're done here, go tell 'em" girlie 🫢


✨ SYNOPSIS ✨

void finish_req (struct iproc_reqctx_s *rctx , int err );

like, that's the whole signature. no notes. πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • rctx β€” the request context. that's her. that's the main character. πŸ‘‘
  • err β€” tells you whether the request was successful or not. yes ma'am, this is the vibe check for success vs. not-success. πŸ”₯

πŸ’– DESCRIPTION πŸ’–

Ensures that cleanup has been done for request. periodt. that's literally the whole job β€” making sure the cleanup already happened before we move on. 🌈

ngl this description is short but she said what she said β€” cleanup = handled. don't skip it. πŸ’€

🧚 SEE ALSO 🧚

all the besties in the same kernel file, ./drivers/crypto/bcm/cipher.c β€” go say hi to them:


and that's the page, bestie!! πŸ“ this one's from ./drivers/crypto/bcm, dated October 2026, and yes the footer still says finish_req(9) because she's consistent like that. mwah πŸ’‹βœ¨

πŸ“¦ where this page comes from