v4l2_m2m_for_each_dst_buf(9)

📦 version 7.3.1, in nixpkgs unstable

💅 v4l2_m2m_for_each_dst_buf (9) — Kernel API Manual ✨

okay so bestie, you found the page for v4l2_m2m_for_each_dst_buf 💖 it lives in the Kernel API Manual, and it's genuinely one of the comfiest little macros in the whole media subsystem, no cap.

🌸 NAME 🌸

v4l2_m2m_for_each_dst_buf — loop over a list of destination ready buffers 🎀 literally just iterating, but make it cute.

✨ SYNOPSIS ✨

v4l2_m2m_for_each_dst_buf (m2m_ctx , b );

that's it. that's the whole call. two things go in, magic happens 🪄

🦋 ARGUMENTS 🦋

  • m2m_ctx — the m2m context that's assigned to the instance, given by struct v4l2_m2m_ctx. she's the main character here, the whole state of your mem2mem setup 👑
  • b — the current buffer, of type struct v4l2_m2m_buffer. this is your loop variable bestie, she gets handed a new buffer each spin around the loop 🔥

👑 SEE ALSO 👑

fr fr there is SO much family here, the whole mem2mem friend group showed up. Kernel file ./include/media/v4l2-mem2mem.h plus:

like, the entire friend group 💀 but honestly? each one ate, go read them 🫶

💡 little vibe check bestie: if you're removing buffers while you loop, you want v4l2_m2m_for_each_dst_buf_safe(9) instead — she's the safe girly for that job 🌈

and that's the page! this one ships from ./include/media, dated October 2026, and it's the v4l2_m2m_for_each_dst_buf(9) page from the Kernel API Manual 🎀 happy iterating, bestie, you're gonna slay those destination buffers ⭐💜

📦 where this page comes from