public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
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,
	Yunke Cao <yunkec@google.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH 0/3] media: uvcvideo: Improvements for UVC metadata
Date: Mon, 16 Mar 2026 13:05:30 +0100	[thread overview]
Message-ID: <6783b48c-9e4c-45ad-a691-9f172c978428@kernel.org> (raw)
In-Reply-To: <20260309-uvc-metadata-dmabuf-v1-0-fc8b87bd29c5@chromium.org>

Hi,

On 9-Mar-26 4:01 PM, Ricardo Ribalda wrote:
> This series introduces some improvements for UVC metadata:
> 
> - Allow bigger sizes of metadata.
> - Refactor the code to avoid invalid pointer arithmetic.
> - Add support for DMABUF
> 
> Cheers!
> 
> Signed-off-by: Ricardo Ribalda <ribalda@chromium.org>

Thank you.

This entire series seems simple/safe enough and looks good to me
from a review pov, so I've pushed this to uvc/for-next now.

While it also rebasing uvc/for-next on top of the latest
media-committers/next .

Regards,

Hans


> ---
> Ricardo Ribalda (3):
>       media: uvcvideo: Enable VB2_DMABUF for metadata stream
>       media: uvcvideo: uvc_queue_to_stream(): Support meta queues
>       media: uvcvideo: Allow userspace to increase the meta buffersize
> 
>  drivers/media/usb/uvc/uvc_isight.c   |  3 ++-
>  drivers/media/usb/uvc/uvc_metadata.c |  9 +++++++--
>  drivers/media/usb/uvc/uvc_queue.c    | 18 ++++++++----------
>  drivers/media/usb/uvc/uvcvideo.h     |  7 +++++--
>  4 files changed, 22 insertions(+), 15 deletions(-)
> ---
> base-commit: a7da7fb57f2a787412da1a62292a17fa00fbfbdf
> change-id: 20260309-uvc-metadata-dmabuf-b98359eec8dd
> 
> Best regards,


  parent reply	other threads:[~2026-03-16 12:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-09 15:01 [PATCH 0/3] media: uvcvideo: Improvements for UVC metadata Ricardo Ribalda
2026-03-09 15:01 ` [PATCH 1/3] media: uvcvideo: Enable VB2_DMABUF for metadata stream Ricardo Ribalda
2026-03-16 11:47   ` Hans de Goede
2026-03-18 19:15   ` Laurent Pinchart
2026-03-09 15:01 ` [PATCH 2/3] media: uvcvideo: uvc_queue_to_stream(): Support meta queues Ricardo Ribalda
2026-03-16 11:49   ` Hans de Goede
2026-03-18 19:18   ` Laurent Pinchart
2026-03-09 15:01 ` [PATCH 3/3] media: uvcvideo: Allow userspace to increase the meta buffersize Ricardo Ribalda
2026-03-16 11:53   ` Hans de Goede
2026-03-18 19:22   ` Laurent Pinchart
2026-03-18 19:29     ` Ricardo Ribalda
2026-03-18 19:36       ` Laurent Pinchart
2026-03-16 12:05 ` Hans de Goede [this message]
2026-03-18 19:23   ` [PATCH 0/3] media: uvcvideo: Improvements for UVC metadata Laurent Pinchart
2026-03-18 20:22     ` [PATCH] media: uvcvideo: Add a stream backpointer in uvc_video_queue Ricardo Ribalda
2026-03-23 22:34       ` Laurent Pinchart

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=6783b48c-9e4c-45ad-a691-9f172c978428@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 \
    --cc=stable@vger.kernel.org \
    --cc=yunkec@google.com \
    /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