v4l2_m2m_dst...emove_by_buf(9)

📦 version 7.3.1, in nixpkgs unstable

💅 v4l2_m2m_dst_buf_remove_by_buf — Kernel API Manual ✨

okay so bestie, welcome to the <pink>Kernel API Manual</pink> 🎀 and today's main character is v4l2_m2m_dst_buf_remove_by_buf, a function whose name is genuinely a whole marathon to type but who is, in fact, super chill and does exactly one thing. iykyk 💅

🌸 NAME 🌸

v4l2_m2m_dst_buf_remove_by_buf — takes off the exact destination buffer from the list of ready buffers. that's it. that's the whole job. no cap 🫶

✨ SYNOPSIS ✨

void v4l2_m2m_dst_buf_remove_by_buf (struct v4l2_m2m_ctx *m2m_ctx ,
struct vb2_v4l2_buffer *vbuf );

not me pointing out that the return type is void — she gives you nothing back, she's a doer, not a returner 😌

🦋 ARGUMENTS 🦋

  • m2m_ctx — the m2m context assigned to the instance, given by struct v4l2_m2m_ctx. this is her home base, her whole personality lives here 💖
  • vbuf — the buffer to be removed. yes, the buffer. the specific one. we're not doing vibes here, we're doing exactness ✨

🌈 SEE ALSO 🌈

genuinely obsessed with how long this list is, like she knows everybody at the party 🎉. Kernel file ./include/media/v4l2-mem2mem.h plus:

like, the whole friend group showed up. iconic behavior honestly 👑

and that's the page, bestie!! go forth and remove exactly one destination buffer, with precision and with slay 💜

sign-off szn: this one lives in ./include/media and it's dated <yellow>October 2026</yellow> — so yeah, she's from the future, we don't question it 🌟💖

v4l2_m2m_dst_buf_remove_by_buf(9) • ./include/media • October 2026 🎀

📦 where this page comes from