From: Randy Dunlap <rdunlap@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: Randy Dunlap <rdunlap@infradead.org>,
Vadim Pasternak <vadimp@nvidia.com>, Pavel Machek <pavel@ucw.cz>,
Lee Jones <lee@kernel.org>,
linux-leds@vger.kernel.org
Subject: [PATCH v2 2/3] leds: leds-mlxcpld: fix struct mlxcpld_led_priv member name
Date: Wed, 28 Feb 2024 23:19:30 -0800 [thread overview]
Message-ID: <20240229071931.7870-3-rdunlap@infradead.org> (raw)
In-Reply-To: <20240229071931.7870-1-rdunlap@infradead.org>
Change "cled" to "cdev" to quieten kernel-doc warnings:
leds-mlxcpld.c:86: warning: Function parameter or struct member 'cdev' not described in 'mlxcpld_led_priv'
leds-mlxcpld.c:86: warning: Excess struct member 'cled' description in 'mlxcpld_led_priv'
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Vadim Pasternak <vadimp@nvidia.com>
Cc: Pavel Machek <pavel@ucw.cz>
Cc: Lee Jones <lee@kernel.org>
Cc: linux-leds@vger.kernel.org
---
v2: make the 3 leds patches a series as requested by Lee;
make the Subject better/unique
drivers/leds/leds-mlxcpld.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -- a/drivers/leds/leds-mlxcpld.c b/drivers/leds/leds-mlxcpld.c
--- a/drivers/leds/leds-mlxcpld.c
+++ b/drivers/leds/leds-mlxcpld.c
@@ -77,7 +77,7 @@ struct mlxcpld_param {
/**
* struct mlxcpld_led_priv - LED private data:
- * @cled: LED class device instance
+ * @cdev: LED class device instance
* @param: LED CPLD access parameters
**/
struct mlxcpld_led_priv {
next prev parent reply other threads:[~2024-02-29 7:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 7:19 [PATCH] leds: fix 3 drivers' kernel-doc warnings Randy Dunlap
2024-02-29 7:19 ` [PATCH v2 1/3] leds: lm3601x: fix struct lm3601_led " Randy Dunlap
2024-02-29 7:19 ` Randy Dunlap [this message]
2024-02-29 7:19 ` [PATCH v2 3/3] leds: mlxreg: drop an excess struct mlxreg_led_data member Randy Dunlap
2024-02-29 7:23 ` [PATCH] leds: fix 3 drivers' kernel-doc warnings Vadim Pasternak
2024-02-29 17:53 ` Lee Jones
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=20240229071931.7870-3-rdunlap@infradead.org \
--to=rdunlap@infradead.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=vadimp@nvidia.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
all inboxes | Powered by JetHome®