From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Linux Media Mailing List <linux-media@vger.kernel.org>
Cc: linuxarm@huawei.com, mauro.chehab@huawei.com,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-kernel@vger.kernel.org
Subject: [PATCH 7/9] media: v4l2-subdev.h: fix a kernel-doc markup
Date: Wed, 30 Sep 2020 08:36:00 +0200 [thread overview]
Message-ID: <c3de5a86c73169459754aa86186ba79446609693.1601447236.git.mchehab+huawei@kernel.org> (raw)
In-Reply-To: <cover.1601447236.git.mchehab+huawei@kernel.org>
As reported by Sphinx:
./Documentation/driver-api/media/v4l2-subdev:490: ./include/media/v4l2-subdev.h:384: WARNING: Unparseable C cross-reference: 'struct'
Invalid C declaration: Expected identifier in nested name, got keyword: struct [error at 6]
struct
------^
The markup there is wrong:
&struct &v4l2_input -> &struct v4l2_input
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
---
include/media/v4l2-subdev.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/media/v4l2-subdev.h b/include/media/v4l2-subdev.h
index 6f6795bab737..1de960bfcab9 100644
--- a/include/media/v4l2-subdev.h
+++ b/include/media/v4l2-subdev.h
@@ -381,7 +381,7 @@ struct v4l2_mbus_frame_desc {
* OUTPUT device. This is ignored by video capture devices.
*
* @g_input_status: get input status. Same as the status field in the
- * &struct &v4l2_input
+ * &struct v4l2_input
*
* @s_stream: used to notify the driver that a video stream will start or has
* stopped.
--
2.26.2
next prev parent reply other threads:[~2020-09-30 6:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-30 6:35 [PATCH 0/9] Address several issues when building media docs with Sphinx 3.x Mauro Carvalho Chehab
2020-09-30 6:35 ` [PATCH 1/9] media: camera-sensor.rst: fix a doc build warning Mauro Carvalho Chehab
2020-09-30 6:35 ` [PATCH 2/9] media: glossary.rst: use the right case for glossary entries Mauro Carvalho Chehab
2020-09-30 6:35 ` [PATCH 3/9] media: docs: ipu3.rst: rely at automarkup extension Mauro Carvalho Chehab
2020-09-30 9:19 ` Sakari Ailus
2020-09-30 6:35 ` [PATCH 4/9] media: dvb-frontends: remove a clone of a kernel-doc markup at zd1301_demod.h Mauro Carvalho Chehab
2020-09-30 6:35 ` [PATCH 5/9] media: v4l2-subdev.rst: get rid of a duplicatd kernel-doc markup Mauro Carvalho Chehab
2020-09-30 6:35 ` [PATCH 6/9] media: cec-core.rst: fix warnings with Sphinx 3.0+ Mauro Carvalho Chehab
2020-09-30 6:36 ` Mauro Carvalho Chehab [this message]
2020-09-30 6:36 ` [PATCH 8/9] media: hist-v4l2.rst: remove struct duplication Mauro Carvalho Chehab
2020-09-30 6:36 ` [PATCH 9/9] media: hist-v4l2.rst: remove :c:`type` from structs and enums Mauro Carvalho Chehab
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=c3de5a86c73169459754aa86186ba79446609693.1601447236.git.mchehab+huawei@kernel.org \
--to=mchehab+huawei@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mauro.chehab@huawei.com \
--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;
as well as URLs for NNTP newsgroup(s).