linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Cox <jc@kynesim.co.uk>
To: Ezequiel Garcia <ezequiel@collabora.com>
Cc: Daniel Almeida <daniel.almeida@collabora.com>,
	Hans Verkuil <hverkuil-cisco@xs4all.nl>,
	linux-media@vger.kernel.org,
	Yunfei Dong <yunfei.dong@mediatek.com>,
	Dikshita Agarwal <dikshita@codeaurora.org>,
	Nicolas Dufresne <nicolas@ndufresne.ca>
Subject: Re: [RFC PATCHv2 02/11] v4l2-ctrls: add support for dynamically allocated arrays.
Date: Wed, 11 Aug 2021 16:59:01 +0100	[thread overview]
Message-ID: <cjs7hg9e457cn775prtsb860lkplvmmj9t@4ax.com> (raw)
In-Reply-To: <123eee90ee3e3fe5227f6ed88defc3818645c83e.camel@collabora.com>

Hi

>[..]
>
>> 
>> 
>>  I tested & used this on my AV1 uapi patches [0] and this feature works just fine as far as I can tell.
>>  
>>  Tested-By: Daniel Almeida <daniel.almeida@collabora.com>
>>  
>>  Can this please be queued for 5.15?
>>  
>
>Hi Daniel,
>
>I believe your reply wasn't plain text so might have been filtered.
>
>Also, I'd say we want to have users actually using the interface,
>before we consider merging it.

What constitutes using? We (Pi) are in the process of adding it in the
next version of our V4L2 H265 decoder (when we update to 5.14), or is it
only used once merged?

(Yes - I really must get round to trying to release our decoder)

Ta

John Cox

  reply	other threads:[~2021-08-11 15:59 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-10 11:36 [RFC PATCHv2 00/11] Dynamic arrays and read-only requests Hans Verkuil
2021-06-10 11:36 ` [RFC PATCHv2 01/11] videodev2.h: add V4L2_CTRL_FLAG_DYNAMIC_ARRAY Hans Verkuil
2022-02-04 17:01   ` Nicolas Dufresne
2021-06-10 11:36 ` [RFC PATCHv2 02/11] v4l2-ctrls: add support for dynamically allocated arrays Hans Verkuil
2021-06-26 16:37   ` Daniel Almeida
2021-06-26 16:42   ` Daniel Almeida
2021-06-28  9:39     ` John Cox
2021-07-05  9:13     ` Hans Verkuil
     [not found]   ` <ccaf0fa9-8be6-c623-61c7-91cb804ca2bf@collabora.com>
2021-08-11 15:46     ` Ezequiel Garcia
2021-08-11 15:59       ` John Cox [this message]
2021-08-27 12:44         ` Ezequiel Garcia
2021-06-10 11:36 ` [RFC PATCHv2 03/11] vivid: add dynamic array test control Hans Verkuil
2021-06-10 11:36 ` [RFC PATCHv2 04/11] media: document read-only requests Hans Verkuil
2021-06-10 11:36 ` [RFC PATCHv2 05/11] videodev2.h: add V4L2_BUF_CAP_SUPPORTS_RO_REQUESTS Hans Verkuil
2021-06-10 11:36 ` [RFC PATCHv2 06/11] videobuf2-core: add vb2_request_buffer_first() Hans Verkuil
2021-06-10 11:36 ` [RFC PATCHv2 07/11] videobuf2-v4l2.c: vb2_request_validate: support RO requests Hans Verkuil
2021-06-10 11:36 ` [RFC PATCHv2 08/11] v4l2-mem2mem.c: allow requests for capture queues Hans Verkuil
2021-06-10 11:36 ` [RFC PATCHv2 09/11] vivid: add ro_requests module option Hans Verkuil
2021-06-10 11:36 ` [RFC PATCHv2 10/11] vim2m: support read-only requests on the capture queue Hans Verkuil
2021-06-10 11:36 ` [RFC PATCHv2 11/11] vicodec: add support for read-only requests Hans Verkuil

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=cjs7hg9e457cn775prtsb860lkplvmmj9t@4ax.com \
    --to=jc@kynesim.co.uk \
    --cc=daniel.almeida@collabora.com \
    --cc=dikshita@codeaurora.org \
    --cc=ezequiel@collabora.com \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=nicolas@ndufresne.ca \
    --cc=yunfei.dong@mediatek.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;
as well as URLs for NNTP newsgroup(s).