From: Randy Dunlap <rdunlap@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: Randy Dunlap <rdunlap@infradead.org>,
James Clark <james.clark@arm.com>,
Tao Zhang <quic_taozha@quicinc.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
coresight@lists.linaro.org
Subject: [PATCH] coresight: coresight.h: add '*' to kernel-doc lines
Date: Thu, 30 Oct 2025 22:42:11 -0700 [thread overview]
Message-ID: <20251031054211.1411151-1-rdunlap@infradead.org> (raw)
kernel-doc reports 2 (kernel-doc) lines in coresight.h that don't have
a beginning '*' in them, so fix these lines.
Warning: include/linux/coresight.h:173 bad line:
connected to @src_port. NULL until the device is created
Warning: include/linux/coresight.h:177 bad line:
needs to be filtered.
Fixes: ec9903d6cc34 ("coresight: Add support for trace filtering by source")
Fixes: d49c9cf15f89 ("coresight: Rename connection members to make the direction explicit")
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
---
Cc: James Clark <james.clark@arm.com>
Cc: Tao Zhang <quic_taozha@quicinc.com>
Cc: Suzuki K Poulose <suzuki.poulose@arm.com>
Cc: coresight@lists.linaro.org
---
include/linux/coresight.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- linux-next-20251016.orig/include/linux/coresight.h
+++ linux-next-20251016/include/linux/coresight.h
@@ -171,11 +171,11 @@ struct coresight_desc {
* @dest_port: destination's input port number @src_port is connected to.
* @dest_fwnode: destination component's fwnode handle.
* @dest_dev: a @coresight_device representation of the component
- connected to @src_port. NULL until the device is created
+ * connected to @src_port. NULL until the device is created
* @link: Representation of the connection as a sysfs link.
* @filter_src_fwnode: filter source component's fwnode handle.
* @filter_src_dev: a @coresight_device representation of the component that
- needs to be filtered.
+ * needs to be filtered.
*
* The full connection structure looks like this, where in_conns store
* references to same connection as the source device's out_conns.
reply other threads:[~2025-10-31 5:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20251031054211.1411151-1-rdunlap@infradead.org \
--to=rdunlap@infradead.org \
--cc=coresight@lists.linaro.org \
--cc=james.clark@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_taozha@quicinc.com \
--cc=suzuki.poulose@arm.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;
as well as URLs for NNTP newsgroup(s).