From: Lee Jones <lee@kernel.org>
To: pavel@ucw.cz, lee@kernel.org, linux-leds@vger.kernel.org,
linux-kernel@vger.kernel.org,
Manuel Fombuena <fombuena@outlook.com>
Subject: Re: [PATCH 0/3] leds-st1202 improvements
Date: Fri, 07 Mar 2025 07:31:21 -0800 [thread overview]
Message-ID: <174136148124.1086011.15222104053418170899.b4-ty@kernel.org> (raw)
In-Reply-To: <CWLP123MB54739F38EF9CFA057021BC2DC5C22@CWLP123MB5473.GBRP123.PROD.OUTLOOK.COM>
On Wed, 26 Feb 2025 17:04:40 +0000, Manuel Fombuena wrote:
> Following the feedback received on the set of patches for leds-st1202 that
> I sent previously, I am sending separately for your consideration those
> that are not fixes with an improved cover letter that hopefully is more
> aligned with the guidelines.
>
> [PATCH 1/3] leds: leds-st1202: initialize hardware before DT node
>
> [...]
Applied, thanks!
[1/3] leds: leds-st1202: initialize hardware before DT node child operations
commit: 8a2727615f9865b69998b3162a76a20c46f97866
[2/3] leds: leds-st1202: spacing and proofreading editing
commit: 2aa76efbbe375be31e0a4db88ef52b4a85c0038e
[3/3] leds: Kconfig: leds-st1202: add select for required LEDS_TRIGGER_PATTERN
commit: d884bb02e14e39e9f269b50b349c37caec001bec
--
Lee Jones [李琼斯]
prev parent reply other threads:[~2025-03-07 15:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 17:04 [PATCH 0/3] leds-st1202 improvements Manuel Fombuena
2025-02-26 17:06 ` [PATCH 1/3] leds: leds-st1202: initialize hardware before DT node child operations Manuel Fombuena
2025-02-26 17:08 ` [PATCH 2/3] leds: leds-st1202: spacing and proofreading editing Manuel Fombuena
2025-02-26 17:12 ` [PATCH 3/3] leds: Kconfig: leds-st1202: add select for required LEDS_TRIGGER_PATTERN Manuel Fombuena
2025-03-06 23:47 ` Lee Jones
2025-03-07 11:34 ` Manuel Fombuena
2025-03-07 15:30 ` Lee Jones
2025-03-07 15:31 ` 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=174136148124.1086011.15222104053418170899.b4-ty@kernel.org \
--to=lee@kernel.org \
--cc=fombuena@outlook.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
/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