s5p_hash_write_iv(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… s5p_hash_write_iv(9) β€” like, the Kernel API Manual page, bestie πŸ’…

okay so this is a page straight out of the Kernel API Manual, and honestly? she's short but she matters. sit down, drink some water, let's get into it 🫢


✨ NAME ✨

s5p_hash_write_iv β€” writes the IV for the next partial/finup op. that's it. that's the whole gig. lowkey iconic for how specific it is πŸ’–


🌸 SYNOPSIS 🌸

void s5p_hash_write_iv (struct ahash_request *req );

returns nothing (void, she gives nothing back, respectfully), takes exactly one thing. no cap.


πŸŽ€ ARGUMENTS πŸŽ€

  • req β€” the AHASH request. yes queen, that's the one you're handing over. it's the request the IV gets written for, periodt.

πŸ¦‹ SEE ALSO πŸ¦‹

so this is the part where the kernel file drops the whole friend group. the file lives at ./drivers/crypto/s5p-sss.c, and here is literally everyone linked off this page β€” no skipping, I promised:

like, the whole squad showed up πŸ’€πŸ‘‘


ngl bestie, this page is tiny and there's no OPTIONS, no environment variables, no exit statuses, no bugs section, no warnings β€” just a NAME, a SYNOPSIS, the one ARGUMENT, and a whole lot of SEE ALSO. do not go looking for more, I checked. she's minimalist 🧚

and that's the whole page, mwah πŸ’‹ β€” brought to you by the source tree at ./drivers/crypto, dated October 2026. bye bestie, go write some IVs 🌈⭐

πŸ“¦ where this page comes from