From: Sakari Ailus <sakari.ailus@iki.fi>
To: linux-media@vger.kernel.org
Subject: [GIT PULL FOR 6.4] Client capability sub-device IOCTL
Date: Fri, 14 Apr 2023 18:10:06 +0300 [thread overview]
Message-ID: <ZDlszuIGxU/yvpN6@valkosipuli.retiisi.eu> (raw)
Hi Mauro,
Here's a PR with just one patch: the client capability sub-device IOCTL.
This will be needed to signal which applications are aware of streams, to
address an age-old issue with reserved fields.
Please pull.
The following changes since commit f100ce3bbd6aa0093075b20b9dbd006686f6aedf:
media: verisilicon: Fix crash when probing encoder (2023-04-13 12:58:55 +0200)
are available in the Git repository at:
git://linuxtv.org/sailus/media_tree.git tags/for-6.4-3-signed
for you to fetch changes up to 9f06f58966d42d3b7a2935fcf511c8ee485546d2:
media: v4l2-subdev: Add new ioctl for client capabilities (2023-04-14 16:41:42 +0300)
----------------------------------------------------------------
Client capability subdev IOCTL for 6.4
----------------------------------------------------------------
Tomi Valkeinen (1):
media: v4l2-subdev: Add new ioctl for client capabilities
.../userspace-api/media/v4l/user-func.rst | 1 +
.../media/v4l/vidioc-subdev-g-client-cap.rst | 83 ++++++++++++++++++++++
drivers/media/v4l2-core/v4l2-subdev.c | 63 ++++++++++++++++
include/media/v4l2-subdev.h | 1 +
include/uapi/linux/v4l2-subdev.h | 21 ++++++
5 files changed, 169 insertions(+)
create mode 100644 Documentation/userspace-api/media/v4l/vidioc-subdev-g-client-cap.rst
--
Kind regards,
Sakari Ailus
next reply other threads:[~2023-04-14 15:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 15:10 Sakari Ailus [this message]
2023-04-14 15:40 ` [GIT PULL FOR 6.4] Client capability sub-device IOCTL (#91306) Jenkins
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=ZDlszuIGxU/yvpN6@valkosipuli.retiisi.eu \
--to=sakari.ailus@iki.fi \
--cc=linux-media@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.