From: Lee Jones <lee@kernel.org>
To: linux-kernel@vger.kernel.org, Randy Dunlap <rdunlap@infradead.org>
Cc: Pavel Machek <pavel@ucw.cz>,
linux-leds@vger.kernel.org, Vadim Pasternak <vadimp@nvidia.com>
Subject: Re: [PATCH] leds: fix 3 drivers' kernel-doc warnings
Date: Thu, 29 Feb 2024 17:53:59 +0000 [thread overview]
Message-ID: <170922923928.1633364.16208391297690612084.b4-ty@kernel.org> (raw)
In-Reply-To: <20240229071931.7870-1-rdunlap@infradead.org>
On Wed, 28 Feb 2024 23:19:28 -0800, Randy Dunlap wrote:
> Fix kernel-doc warnings in 3 leds drivers:
>
> [PATCH v2 1/3] leds: lm3601x: fix struct lm3601_led kernel-doc warnings
> [PATCH v2 2/3] leds: leds-mlxcpld: fix struct mlxcpld_led_priv member name
> [PATCH v2 3/3] leds: mlxreg: drop an excess struct mlxreg_led_data member
>
> drivers/leds/flash/leds-lm3601x.c | 3 +--
> drivers/leds/leds-mlxcpld.c | 2 +-
> drivers/leds/leds-mlxreg.c | 1 -
> 3 files changed, 2 insertions(+), 4 deletions(-)
>
> [...]
Applied, thanks!
[1/3] leds: lm3601x: fix struct lm3601_led kernel-doc warnings
commit: 5edfca391c5fb2fa12c438aee5ccbe0b22713f31
[2/3] leds: leds-mlxcpld: fix struct mlxcpld_led_priv member name
commit: 0e225365753c8824b720588252458be87a0841a1
[3/3] leds: mlxreg: drop an excess struct mlxreg_led_data member
commit: 5764ba63b4256008d59d178dfbec9851cf9a7b92
--
Lee Jones [李琼斯]
prev parent reply other threads:[~2024-02-29 17:54 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 ` [PATCH v2 2/3] leds: leds-mlxcpld: fix struct mlxcpld_led_priv member name Randy Dunlap
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 [this message]
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=170922923928.1633364.16208391297690612084.b4-ty@kernel.org \
--to=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rdunlap@infradead.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).