From: Paul Kocialkowski <paulk@sys-base.io>
To: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hverkuil@xs4all.nl>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Nicolas Dufresne <nicolas.dufresne@collabora.com>,
Paul Kocialkowski <paulk@sys-base.io>
Subject: [PATCH v2 0/4] Minor V4L2 Headers and Codec Doc Cleanups
Date: Sun, 24 Aug 2025 20:07:31 +0200 [thread overview]
Message-ID: <20250824180735.765587-1-paulk@sys-base.io> (raw)
Changes since v1:
- Added minor codec control cleanups;
- Added documentation about h.264 frame-wide type flags
Paul Kocialkowski (4):
media: uapi: Move colorimetry controls at the end of the file
media: uapi: Cleanup tab after define in headers
media: uapi: v4l2-controls: Cleanup codec definitions
Documentation: media: Document
V4L2_H264_DECODE_PARAM_FLAG_PFRAME/BFRAME
.../media/v4l/ext-ctrls-codec-stateless.rst | 8 +-
include/uapi/linux/v4l2-controls.h | 121 +++++++++---------
include/uapi/linux/videodev2.h | 18 +--
3 files changed, 75 insertions(+), 72 deletions(-)
--
2.50.1
next reply other threads:[~2025-08-24 18:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-24 18:07 Paul Kocialkowski [this message]
2025-08-24 18:07 ` [PATCH v2 1/4] media: uapi: Move colorimetry controls at the end of the file Paul Kocialkowski
2025-08-28 18:45 ` Nicolas Dufresne
2025-08-24 18:07 ` [PATCH v2 2/4] media: uapi: Cleanup tab after define in headers Paul Kocialkowski
2025-08-28 18:46 ` Nicolas Dufresne
2025-08-24 18:07 ` [PATCH v2 3/4] media: uapi: v4l2-controls: Cleanup codec definitions Paul Kocialkowski
2025-08-28 18:46 ` Nicolas Dufresne
2025-08-24 18:07 ` [PATCH v2 4/4] Documentation: media: Document V4L2_H264_DECODE_PARAM_FLAG_PFRAME/BFRAME Paul Kocialkowski
2025-08-28 20:42 ` Nicolas Dufresne
2025-08-29 14:15 ` Paul Kocialkowski
2025-08-30 11:29 ` Dmitry Osipenko
2025-08-29 20:40 ` [PATCH v2 0/4] Minor V4L2 Headers and Codec Doc Cleanups Nicolas Dufresne
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=20250824180735.765587-1-paulk@sys-base.io \
--to=paulk@sys-base.io \
--cc=hverkuil@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=nicolas.dufresne@collabora.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
all inboxes | Powered by JetHome®