From: Linus Walleij <linus.walleij@linaro.org>
To: "Pali Rohár" <pali@kernel.org>
Cc: "Pavel Machek" <pavel@ucw.cz>, "Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Marek Behún" <kabel@kernel.org>,
linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] leds: syscon: Implement support for active-low property
Date: Tue, 8 Nov 2022 13:42:34 +0100 [thread overview]
Message-ID: <CACRpkdad6WDo7rGfa4MW8zz0mLXmcPHo+SEC-yLQnRz_kdrryA@mail.gmail.com> (raw)
In-Reply-To: <20221101223255.rhzerarzld45xfjh@pali>
On Tue, Nov 1, 2022 at 11:33 PM Pali Rohár <pali@kernel.org> wrote:
> On Sunday 09 October 2022 13:40:43 Pali Rohár wrote:
> > On Wednesday 31 August 2022 13:49:36 Pali Rohár wrote:
> > > On Friday 26 August 2022 10:05:26 Linus Walleij wrote:
> > > > On Thu, Aug 18, 2022 at 7:25 PM Pali Rohár <pali@kernel.org> wrote:
> > > >
> > > > > This new active-low property specify that LED has inverted logic
> > > > > (0 - enable LED, 1 - disable LED).
> > > > >
> > > > > Signed-off-by: Pali Rohár <pali@kernel.org>
> > > >
> > > > Acked-by: Linus Walleij <linus.walleij@linaro.org>
> > > >
> > > > Yours,
> > > > Linus Walleij
> > >
> > > Is something else needed for this patch series?
> >
> > PING?
>
> PING?
If the LED subsystem isn't working consider sending the patch to the
SoC tree with a notice that they apply it instead and why.
Yours,
Linus Walleij
next prev parent reply other threads:[~2022-11-08 12:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 17:25 [PATCH 1/2] dt-bindings: leds: register-bit-led: Add active-low property Pali Rohár
2022-08-18 17:25 ` [PATCH 2/2] leds: syscon: Implement support for " Pali Rohár
2022-08-26 8:05 ` Linus Walleij
2022-08-31 11:49 ` Pali Rohár
2022-10-09 11:40 ` Pali Rohár
2022-11-01 22:32 ` Pali Rohár
2022-11-08 12:42 ` Linus Walleij [this message]
2022-08-19 6:46 ` [PATCH 1/2] dt-bindings: leds: register-bit-led: Add " Krzysztof Kozlowski
2022-08-19 6:56 ` Pali Rohár
2022-08-19 8:08 ` Pavel Machek
2022-08-19 8:38 ` Krzysztof Kozlowski
2022-08-19 8:42 ` Pali Rohár
2022-08-19 9:08 ` Krzysztof Kozlowski
2022-08-19 9:11 ` Pali Rohár
2022-08-19 8:35 ` Linus Walleij
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=CACRpkdad6WDo7rGfa4MW8zz0mLXmcPHo+SEC-yLQnRz_kdrryA@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=kabel@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pali@kernel.org \
--cc=pavel@ucw.cz \
--cc=robh+dt@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 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 NNTP newsgroup(s).