From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
Cc: linux-media@vger.kernel.org,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>,
Jacopo Mondi <jacopo.mondi@ideasonboard.com>
Subject: Re: [PATCH] media: v4l2-subdev: Fix missing kerneldoc for client_caps
Date: Thu, 18 May 2023 09:41:31 +0100 [thread overview]
Message-ID: <20230518094131.7d5057b7@sal.lan> (raw)
In-Reply-To: <20230418105924.126608-1-tomi.valkeinen@ideasonboard.com>
Em Tue, 18 Apr 2023 13:59:24 +0300
Tomi Valkeinen <tomi.valkeinen@ideasonboard.com> escreveu:
> Add missing kernel doc for the new 'client_caps' field in struct
> v4l2_subdev_fh.
>
> Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
> ---
> include/media/v4l2-subdev.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/include/media/v4l2-subdev.h b/include/media/v4l2-subdev.h
> index cfd19e72d0fc..9d0a6a993fb0 100644
> --- a/include/media/v4l2-subdev.h
> +++ b/include/media/v4l2-subdev.h
> @@ -1119,6 +1119,7 @@ struct v4l2_subdev {
> * @vfh: pointer to &struct v4l2_fh
> * @state: pointer to &struct v4l2_subdev_state
> * @owner: module pointer to the owner of this file handle
> + * @client_caps: bitmask of V4L2_SUBDEV_CLIENT_CAP_*
Did you actually check this patch? Adding an asterisk at the end
should hit a Sphinx warning, as asterisk is the italic markup.
So, it seems to me that this patch is actually replacing one warning
by another one!
Also, it is not pointing the patch this was supposed to be fixing.
Btw, I actually did a fix for it already, while I was working to fix
some issues on Jenkins. See below. If you're ok with that, please add
your A-B or R-B. Otherwise, submit another one, after testing that
Sphinx won't be printing an additional warning.
Regards,
Mauro
---
[PATCH] media: v4l2-subdev.h: document client_caps at struct v4l2_subdev_fh
Gets rid of this documentation warning:
./include/media/v4l2-subdev.h:1130: warning: Function parameter or member 'client_caps' not described in 'v4l2_subdev_fh'
By adding a documentation about such new field.
Fixes: f57fa2959244 ("media: v4l2-subdev: Add new ioctl for client capabilities")
Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
diff --git a/include/media/v4l2-subdev.h b/include/media/v4l2-subdev.h
index cfd19e72d0fc..62362da0d604 100644
--- a/include/media/v4l2-subdev.h
+++ b/include/media/v4l2-subdev.h
@@ -1119,6 +1119,9 @@ struct v4l2_subdev {
* @vfh: pointer to &struct v4l2_fh
* @state: pointer to &struct v4l2_subdev_state
* @owner: module pointer to the owner of this file handle
+ * @client_caps:
+ * client capabilities to inform the kernel of the behavior
+ * of the client as set by VIDIOC_SUBDEV_S_CLIENT_CAP.
*/
struct v4l2_subdev_fh {
struct v4l2_fh vfh;
next prev parent reply other threads:[~2023-05-18 8:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 10:59 [PATCH] media: v4l2-subdev: Fix missing kerneldoc for client_caps Tomi Valkeinen
2023-04-18 14:33 ` Laurent Pinchart
2023-05-08 10:00 ` Sakari Ailus
2023-05-18 8:41 ` Mauro Carvalho Chehab [this message]
2023-05-18 11:22 ` Tomi Valkeinen
2023-05-19 7:47 ` Sakari Ailus
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=20230518094131.7d5057b7@sal.lan \
--to=mchehab@kernel.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=jacopo.mondi@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=tomi.valkeinen@ideasonboard.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