This is an automatic generated email to let you know that the following patch 
were queued:

Subject: media: vidioc-subdev-g-client-cap.rst: document struct 
v4l2_subdev_client_capability
Author:  Hans Verkuil <hverkuil-ci...@xs4all.nl>
Date:    Fri Dec 15 10:38:29 2023 +0100

The struct v4l2_subdev_client_capability was never actually documented,
only the capability flags were documented.

Add this.

Signed-off-by: Hans Verkuil <hverkuil-ci...@xs4all.nl>

 .../media/v4l/vidioc-subdev-g-client-cap.rst              | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

---

diff --git 
a/Documentation/userspace-api/media/v4l/vidioc-subdev-g-client-cap.rst 
b/Documentation/userspace-api/media/v4l/vidioc-subdev-g-client-cap.rst
index 810b6a859dc8..da4a358ce762 100644
--- a/Documentation/userspace-api/media/v4l/vidioc-subdev-g-client-cap.rst
+++ b/Documentation/userspace-api/media/v4l/vidioc-subdev-g-client-cap.rst
@@ -61,6 +61,21 @@ been accepted. A common case for the kernel not accepting a 
capability is that
 the kernel is older than the headers the userspace uses, and thus the 
capability
 is unknown to the kernel.
 
+.. tabularcolumns:: |p{1.5cm}|p{2.9cm}|p{12.9cm}|
+
+.. c:type:: v4l2_subdev_client_capability
+
+.. flat-table:: struct v4l2_subdev_client_capability
+    :header-rows:  0
+    :stub-columns: 0
+    :widths:       3 4 20
+
+    * - __u64
+      - ``capabilities``
+      - Sub-device client capabilities of the opened device.
+
+.. tabularcolumns:: |p{6.8cm}|p{2.4cm}|p{8.1cm}|
+
 .. flat-table:: Client Capabilities
     :header-rows:  1
 

Reply via email to