From: Hans de Goede <hansg@kernel.org>
To: Ricardo Ribalda <ribalda@chromium.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Guennadi Liakhovetski <guennadi.liakhovetski@intel.com>
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] media: uvcvideo: Avoid partial metadata buffers
Date: Mon, 11 May 2026 16:16:56 +0200 [thread overview]
Message-ID: <8134fd03-7085-4572-ab1e-402d772a0921@kernel.org> (raw)
In-Reply-To: <20260417-uvc-meta-partial-v2-0-31d274af7d2d@chromium.org>
Hi,
On 17-Apr-26 07:19, Ricardo Ribalda wrote:
> The current code can lead to partial metadata buffers when the metadata
> queue transitions from empty to ready. Fix that.
>
> Signed-off-by: Ricardo Ribalda <ribalda@chromium.org>
I've merged this in my local uvc/for-next branch.
I'll push this out to gitlab for CI later today.
Regards,
Hans
> ---
> Changes in v2: (Thanks Laurent)
> - Transition to UVC_BUF_STATE_ACTIVE with the data buffer
> - Link to v1: https://lore.kernel.org/r/20260415-uvc-meta-partial-v1-0-a0acc79a6300@chromium.org
>
> ---
> Ricardo Ribalda (2):
> media: uvcvideo: Do not open code uvc_queue_get_current_buffer
> media: uvcvideo: Avoid partial metadata buffers
>
> drivers/media/usb/uvc/uvc_video.c | 23 +++++++++++------------
> 1 file changed, 11 insertions(+), 12 deletions(-)
> ---
> base-commit: 2e9a8a967f836cf879f35c7434025de265826cc1
> change-id: 20260415-uvc-meta-partial-a5767866d0e0
>
> Best regards,
prev parent reply other threads:[~2026-05-11 14:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-17 5:19 [PATCH v2 0/2] media: uvcvideo: Avoid partial metadata buffers Ricardo Ribalda
2026-04-17 5:19 ` [PATCH v2 1/2] media: uvcvideo: Do not open code uvc_queue_get_current_buffer Ricardo Ribalda
2026-05-11 13:28 ` Hans de Goede
2026-04-17 5:19 ` [PATCH v2 2/2] media: uvcvideo: Avoid partial metadata buffers Ricardo Ribalda
2026-05-11 13:29 ` Hans de Goede
2026-05-11 14:16 ` Hans de Goede [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8134fd03-7085-4572-ab1e-402d772a0921@kernel.org \
--to=hansg@kernel.org \
--cc=guennadi.liakhovetski@intel.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=ribalda@chromium.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox