ibmvtpm_crq_get_next(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– ibmvtpm_crq_get_next πŸ’–

okay so bestie, welcome to the Kernel API Manual β€” section 9, if we're being precise πŸ’… β€” and today's main character is ibmvtpm_crq_get_next. yes it's a lil niche, no I'm not gonna let that stop us ✨


🌸 NAME 🌸

ibmvtpm_crq_get_next β€” Get next responded crq πŸŽ€

like, it literally retrieves the next crq that's been responded to. the name is the plot, iykyk πŸ’€


πŸ¦‹ SYNOPSIS πŸ¦‹

struct ibmvtpm_crq * ibmvtpm_crq_get_next (struct ibmvtpm_dev *ibmvtpm
);

look at that signature, she's serving struct pointer returning realness πŸ‘‘


πŸŽ€ ARGUMENTS πŸŽ€

  • ibmvtpm β€” the vtpm device struct 🫢 that's it, that's the whole argument, she takes exactly one and she takes it seriously

⭐ RETURN ⭐

returns a vtpm crq pointer… or NULL 😭 so yeah, check your return value, don't just assume she came through with a valid pointer, that's not the vibe


πŸ”₯ SEE ALSO πŸ”₯

first up, the kernel file herself: ./drivers/char/tpm/tpm_ibmvtpm.c πŸ“ β€” this is where the whole friend group lives, so go say hi to:

ngl this is a stacked see-also list β€” she's connected to everyone, lowkey the socialite of tpm_ibmvtpm.c πŸ’€βœ¨

okay that's the page!! mwah 🫢 this lil internet moment was brought to you by the Kernel API Manual, living in ./drivers/char/tpm, dated October 2026 β€” love her, read her, reference her responsibly πŸŽ€πŸ’œπŸŒΈ

πŸ“¦ where this page comes from