From: Peter Rosin <peda@axentia.se>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Aswath Govindraju <a-govindraju@ti.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [PATCH 6/6] mux: Fix struct mux_state kernel-doc comment
Date: Sun, 2 Jan 2022 23:38:54 +0100 [thread overview]
Message-ID: <2f5b3fa0-1722-e7ca-dc88-a0e870cbc5a5@axentia.se> (raw)
In-Reply-To: <94ab71e1-2e68-def2-95b8-33162172f65c@axentia.se>
From: Yang Li <yang.lee@linux.alibaba.com>
A warning is reported because a colon was dropped, it is found by running
scripts/kernel-doc, which is caused by using 'make W=1'.
drivers/mux/core.c:44: warning: Function parameter or member 'state' not
described in 'mux_state'
Reported-by: Abaci Robot <abaci@linux.alibaba.com>
Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>
Signed-off-by: Peter Rosin <peda@axentia.se>
---
drivers/mux/core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mux/core.c b/drivers/mux/core.c
index fc339b0064e9..11a5c488c812 100644
--- a/drivers/mux/core.c
+++ b/drivers/mux/core.c
@@ -33,7 +33,7 @@
* struct mux_state - Represents a mux controller state specific to a given
* consumer.
* @mux: Pointer to a mux controller.
- * @state State of the mux to be selected.
+ * @state: State of the mux to be selected.
*
* This structure is specific to the consumer that acquires it and has
* information specific to that consumer.
--
2.20.1
next prev parent reply other threads:[~2022-01-02 22:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-02 22:34 mux for 5.17-rc1 Peter Rosin
2022-01-02 22:38 ` [PATCH 1/6] dt-bindings: ti-serdes-mux: Add defines for J721S2 SoC Peter Rosin
2022-01-02 22:38 ` [PATCH 2/6] dt-bindings: mux: Document mux-states property Peter Rosin
2022-01-02 22:38 ` [PATCH 3/6] mux: Add support for reading mux state from consumer DT node Peter Rosin
2022-01-03 12:43 ` Greg Kroah-Hartman
2022-01-03 13:05 ` Aswath Govindraju
2022-01-03 13:23 ` Greg Kroah-Hartman
2022-01-02 22:38 ` [PATCH 4/6] mux: add missing mux_state_get Peter Rosin
2022-01-03 12:42 ` Greg Kroah-Hartman
2022-01-03 17:26 ` Peter Rosin
2022-01-06 14:41 ` Greg Kroah-Hartman
2022-01-07 7:10 ` Peter Rosin
2022-01-02 22:38 ` [PATCH 5/6] mux: fix grammar, missing "is" Peter Rosin
2022-01-03 12:37 ` Greg Kroah-Hartman
2022-01-02 22:38 ` Peter Rosin [this message]
2022-01-03 12:46 ` mux for 5.17-rc1 Greg Kroah-Hartman
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=2f5b3fa0-1722-e7ca-dc88-a0e870cbc5a5@axentia.se \
--to=peda@axentia.se \
--cc=a-govindraju@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®