From: Ruslan Koreev <koreev.r@gmail.com>
To: Lee Jones <lee@kernel.org>
Cc: pavel@kernel.org, rillian.grant@gmail.com,
linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] leds: flash: lm3643: Return to standby when the last output is switched off
Date: Sun, 18 Oct 2026 01:46:16 +0300 [thread overview]
Message-ID: <20261017224617.430992-1-koreev.r@gmail.com> (raw)
In-Reply-To: <179198511712.839288.17752967041610699661@kernel.org>
Hi Lee,
On Wed, Oct 14, 2026 at 04:21:51PM +0100, Lee Jones wrote:
> Given that the base series hasn't been merged yet, please coordinate with
> Rillian to fold these fixes directly into the next version of the original
> series rather than sending fix-up patches on top of an unapplied RFC.
Rillian already folded the standby fix into the driver in patch 2/4 and
included the ACPI LED description as patch 3/4. Both were included in v2
and carried forward into v3, posted on October 11:
https://lore.kernel.org/linux-leds/20261011191026.149338-1-rillian.grant@gmail.com/
Please treat my original two-patch series as superseded.
Thanks,
Ruslan
next prev parent reply other threads:[~2026-10-17 22:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260821083620.68324-1-rillian.grant@gmail.com>
2026-08-21 8:36 ` [RFC PATCH 1/2] dt-bindings: leds: Document TI LM3643 dual LED flash driver Rillian Grant
2026-08-21 8:36 ` [RFC PATCH 2/2] leds: flash: Add support for the " Rillian Grant
2026-09-24 17:20 ` [PATCH 0/2] leds: flash: lm3643: standby fix and ACPI LED description Ruslan Koreev
2026-09-24 17:20 ` [PATCH 1/2] leds: flash: lm3643: Return to standby when the last output is switched off Ruslan Koreev
2026-10-14 15:21 ` Lee Jones
2026-10-17 22:46 ` Ruslan Koreev [this message]
2026-09-24 17:20 ` [PATCH 2/2] leds: flash: lm3643: Describe the LED of ACPI boards without LED nodes Ruslan Koreev
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=20261017224617.430992-1-koreev.r@gmail.com \
--to=koreev.r@gmail.com \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@kernel.org \
--cc=rillian.grant@gmail.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®