From: Lee Jones <lee@kernel.org>
To: "Escala, Edelweise" <Edelweise.Escala@analog.com>
Cc: Pavel Machek <pavel@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
"linux-leds@vger.kernel.org" <linux-leds@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Conor Dooley <conor.dooley@microchip.com>
Subject: Re: [PATCH v5 0/2] Add Support for LTC3219 18 Channel LED Driver
Date: Thu, 12 Feb 2026 08:28:41 +0000 [thread overview]
Message-ID: <20260212082841.GB9065@google.com> (raw)
In-Reply-To: <DS0PR03MB72285F5F9526B1020188CE3FED60A@DS0PR03MB7228.namprd03.prod.outlook.com>
On Thu, 12 Feb 2026, Escala, Edelweise wrote:
> Hi all,
>
> I’d like to kindly follow up on this patch series.
> Is there any additional feedback or action needed from my side to help move it forward upstream?
>
> Thank you for your time and consideration.
Yes, probably.
However, the merge-window is currently open which mean maintainers and
reviewers are either concentrating on activities or taking a break.
We'll get around to reviewing your submission soon.
--
Lee Jones [李琼斯]
prev parent reply other threads:[~2026-02-12 8:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 6:25 [PATCH v5 0/2] Add Support for LTC3219 18 Channel LED Driver Edelweise Escala
2026-01-26 6:25 ` [PATCH v5 1/2] dt-bindings: leds: Add LTC3220 18 channel " Edelweise Escala
2026-01-26 6:25 ` [PATCH v5 2/2] leds: ltc3220: Add Support for " Edelweise Escala
2026-03-06 11:15 ` Lee Jones
2026-03-07 6:40 ` Escala, Edelweise
2026-04-10 9:17 ` Escala, Edelweise
2026-02-12 0:45 ` [PATCH v5 0/2] Add Support for LTC3219 18 Channel " Escala, Edelweise
2026-02-12 8:28 ` 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=20260212082841.GB9065@google.com \
--to=lee@kernel.org \
--cc=Edelweise.Escala@analog.com \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@kernel.org \
--cc=robh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.