From: Jonathan Corbet <corbet@lwn.net>
To: linux-doc@vger.kernel.org
Cc: Jonathan Corbet <corbet@lwn.net>
Subject: [PATCH 3/7] docs: Do not seek kerneldoc comments in hw-consumer.h
Date: Mon, 27 May 2019 16:26:54 -0600 [thread overview]
Message-ID: <20190527222658.27304-4-corbet@lwn.net> (raw)
In-Reply-To: <20190527222658.27304-1-corbet@lwn.net>
There are no kerneldoc comments here, so looking for them just yields a
warning in the docs build.
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
---
Documentation/driver-api/iio/hw-consumer.rst | 1 -
1 file changed, 1 deletion(-)
diff --git a/Documentation/driver-api/iio/hw-consumer.rst b/Documentation/driver-api/iio/hw-consumer.rst
index e0fe0b98230e..819fb9edc005 100644
--- a/Documentation/driver-api/iio/hw-consumer.rst
+++ b/Documentation/driver-api/iio/hw-consumer.rst
@@ -45,7 +45,6 @@ A typical IIO HW consumer setup looks like this::
More details
============
-.. kernel-doc:: include/linux/iio/hw-consumer.h
.. kernel-doc:: drivers/iio/buffer/industrialio-hw-consumer.c
:export:
--
2.21.0
next prev parent reply other threads:[~2019-05-27 22:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-27 22:26 [PATCH 0/7] The eternal battle against docs-build warnings Jonathan Corbet
2019-05-27 22:26 ` [PATCH 1/7] docs: Do not seek comments in kernel/rcu/tree_plugin.h Jonathan Corbet
2019-05-27 22:26 ` [PATCH 2/7] docs: Fix a misdirected kerneldoc directive Jonathan Corbet
2019-05-27 22:26 ` Jonathan Corbet [this message]
2019-05-27 22:26 ` [PATCH 4/7] docs: No structured comments in target_core_device.c Jonathan Corbet
2019-05-27 22:26 ` [PATCH 5/7] docs: no structured comments in fs/file_table.c Jonathan Corbet
2019-05-27 22:26 ` [PATCH 6/7] docs: No structured comments in include/linux/interconnect.h Jonathan Corbet
2019-05-27 22:26 ` [PATCH 7/7] kernel-doc: always name missing kerneldoc sections Jonathan Corbet
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=20190527222658.27304-4-corbet@lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox