From: Fritz Koenig <frkoenig@chromium.org>
To: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
Fritz Koenig <frkoenig@chromium.org>
Subject: [PATCH v2] Documentation: media: Fix v4l2_vp9_segmentation
Date: Tue, 24 Mar 2026 14:00:06 -0700 [thread overview]
Message-ID: <20260324-try-2-v2-1-eedbd0d3cec5@chromium.org> (raw)
feature_data is defined as __s16 in the header.
Signed-off-by: Fritz Koenig <frkoenig@chromium.org>
---
Changes in v2:
- Correct author/signoff (@google.com -> @chromium.org)
- Link to v1: https://lore.kernel.org/r/20260324-v4l2-doc-fix-v1-1-1b4773c391df@google.com
---
Documentation/userspace-api/media/v4l/ext-ctrls-codec-stateless.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/userspace-api/media/v4l/ext-ctrls-codec-stateless.rst b/Documentation/userspace-api/media/v4l/ext-ctrls-codec-stateless.rst
index 3b1e05c6eb13..d7a3b8ef03a7 100644
--- a/Documentation/userspace-api/media/v4l/ext-ctrls-codec-stateless.rst
+++ b/Documentation/userspace-api/media/v4l/ext-ctrls-codec-stateless.rst
@@ -1877,7 +1877,7 @@ params syntax' of the :ref:`vp9` specification for more details.
:stub-columns: 0
:widths: 1 1 2
- * - __u8
+ * - __s16
- ``feature_data[8][4]``
- Data attached to each feature. Data entry is only valid if the feature
is enabled. The array shall be indexed with segment number as the first dimension
---
base-commit: e3c33bc767b5512dbfec643a02abf58ce608f3b2
change-id: 20260324-try-2-0f63be5786ef
Best regards,
--
Fritz Koenig <frkoenig@chromium.org>
next reply other threads:[~2026-03-24 21:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 21:00 Fritz Koenig [this message]
[not found] ` <69c30f82.050a0220.1ae388.4e92@mx.google.com>
2026-03-24 23:06 ` [v2] Documentation: media: Fix v4l2_vp9_segmentation Fritz Koenig
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=20260324-try-2-v2-1-eedbd0d3cec5@chromium.org \
--to=frkoenig@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.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