tpm_buf_append(9)

📦 version 7.3.1, in nixpkgs unstable

🌸 tpm_buf_append — bestie's guide to the kernel API manual, section 9 💅

okay so this is tpm_buf_append from the Kernel API Manual (that's the manual name, hi, welcome to section 9) and honestly? she's a little workhorse and I'm obsessed. ✨

✨ NAME ✨

tpm_buf_append — append data to an initialized buffer 🎀

like, the buffer has already been initialized, okay? that part is not her job. don't come for her. 💅

🦋 SYNOPSIS 🦋

void tpm_buf_append (struct tpm_buf *buf , const u8 *new_data , u16
new_length );

literally the whole signature, verbatim, no notes. void return, so she gives you nothing back — she just does the thing and you move on with your life. main character energy fr fr. 👑

💖 ARGUMENTS 💖

  • buf — a tpm_buf. that's it, that's the description. your buffer. the vessel. the moment. 🫶
  • new_data — a data blob ✨ just... a blob of data. no cap.
  • new_length — size of the appended data. it's a u16, bestie, so it's the length of the stuff you're appending. the way that she needs this to know how much of the blob matters? iconic. 😭

🌈 SEE ALSO 🌈

the kernel file lives at ./drivers/char/tpm/tpm-buf.c and, ngl, there's a whole friend group over there. go say hi to all of them:

like, the read squad and the init squad and the reset squad all showed up. it's giving family reunion. 🧚 💜

💀 reminder: tpm_buf_append expects an initialized buffer — that's in the NAME section, not my invention, so don't blame me when the vibes go sideways.

okay that's the whole page, no filler, every single detail intact, and now the cute sign-off: this one comes from ./drivers/char/tpm, dated October 2026 🍓 — take care of her, she appends. bye bestie!! 🦋💖

📦 where this page comes from