From: "Arnd Bergmann" <arnd@arndb.de>
To: "Pali Rohár" <pali@kernel.org>,
"Linus Walleij" <linus.walleij@linaro.org>
Cc: Lee Jones <lee@kernel.org>,
linux-kernel@vger.kernel.org, Nicholas Piggin <npiggin@gmail.com>,
soc@kernel.org, Pavel Machek <pavel@ucw.cz>,
linuxppc-dev@lists.ozlabs.org, linux-leds@vger.kernel.org
Subject: Re: [PATCH RESEND 0/8] Resend LED patches
Date: Fri, 20 Jan 2023 17:41:49 +0100 [thread overview]
Message-ID: <db008af4-2918-4458-aa68-2392674475c8@app.fastmail.com> (raw)
In-Reply-To: <20221226123630.6515-1-pali@kernel.org>
On Mon, Dec 26, 2022, at 13:36, Pali Rohár wrote:
> Linus Walleij suggested me to send these patches to SoC tree [1]
> instead. So I'm doing it.
>
> This patch series contains LED patches which are on the linux-leds
> mailing list for a long time without any future movement. Could you
> please handle them here via SoC tree? Thanks.
>
> [1] -
> https://lore.kernel.org/linux-leds/CACRpkdad6WDo7rGfa4MW8zz0mLXmcPHo+SEC-yLQnRz_kdrryA@mail.gmail.com/
I'm going through the backlog of patches sent to soc@kernel.org
and came across this series. While I don't mind taking these
patches through the soc tree in principle, it is important
that this is only done as an exception, and with all the
relevant parties on Cc.
In particular, the original series that you got no
feedback for did not include the arch/powerpc/ changes,
and I would assume those should go through the powerpc
tree anyway. We have recently decided to take
risc-v and loongarch dts changes through the soc
tree, and I don't mind doing it for powerpc as well
if the powerpc maintainers prefer that, but this is
not something we have even discussed so far.
I've added everyone to Cc on this mail, but please
resend the series once more so everyone has the patches,
and then we can decide who will pick up what.
Arnd
>
> Marek Behún (3):
> leds: turris-omnia: support HW controlled mode via private trigger
> leds: turris-omnia: initialize multi-intensity to full
> leds: turris-omnia: change max brightness from 255 to 1
>
> Pali Rohár (5):
> dt-bindings: leds: register-bit-led: Add active-low property
> leds: syscon: Implement support for active-low property
> powerpc/85xx: DTS: Add CPLD definitions for P1021RDB Combo Board CPL
> Design
> dt-bindings: leds: Add cznic,turris1x-leds.yaml binding
> leds: Add support for Turris 1.x LEDs
>
> .../testing/sysfs-class-led-driver-turris1x | 31 ++
> .../bindings/leds/cznic,turris1x-leds.yaml | 118 +++++
> .../bindings/leds/register-bit-led.yaml | 5 +
> arch/powerpc/boot/dts/fsl/p1020mbg-pc.dtsi | 92 ++++
> arch/powerpc/boot/dts/fsl/p1020mbg-pc_32b.dts | 6 +-
> arch/powerpc/boot/dts/fsl/p1020mbg-pc_36b.dts | 6 +-
> arch/powerpc/boot/dts/fsl/p1020rdb-pd.dts | 44 +-
> arch/powerpc/boot/dts/fsl/p1020utm-pc.dtsi | 37 ++
> arch/powerpc/boot/dts/fsl/p1020utm-pc_32b.dts | 4 +-
> arch/powerpc/boot/dts/fsl/p1020utm-pc_36b.dts | 4 +-
> arch/powerpc/boot/dts/fsl/p1021rdb-pc.dtsi | 37 ++
> arch/powerpc/boot/dts/fsl/p1021rdb-pc_32b.dts | 5 +-
> arch/powerpc/boot/dts/fsl/p1021rdb-pc_36b.dts | 5 +-
> arch/powerpc/boot/dts/fsl/p2020rdb-pc.dtsi | 33 +-
> drivers/leds/Kconfig | 10 +
> drivers/leds/Makefile | 1 +
> drivers/leds/leds-syscon.c | 14 +-
> drivers/leds/leds-turris-1x.c | 474 ++++++++++++++++++
> drivers/leds/leds-turris-omnia.c | 46 +-
> 19 files changed, 945 insertions(+), 27 deletions(-)
> create mode 100644
> Documentation/ABI/testing/sysfs-class-led-driver-turris1x
> create mode 100644
> Documentation/devicetree/bindings/leds/cznic,turris1x-leds.yaml
> create mode 100644 drivers/leds/leds-turris-1x.c
>
> --
> 2.20.1
next parent reply other threads:[~2023-01-20 16:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221226123630.6515-1-pali@kernel.org>
2023-01-20 16:41 ` Arnd Bergmann [this message]
2023-01-20 17:15 ` [PATCH RESEND 0/8] Resend LED patches Lee Jones
2023-01-20 17:47 ` Arnd Bergmann
2023-01-20 20:02 ` Lee Jones
2023-01-26 20:07 ` 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=db008af4-2918-4458-aa68-2392674475c8@app.fastmail.com \
--to=arnd@arndb.de \
--cc=lee@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.com \
--cc=pali@kernel.org \
--cc=pavel@ucw.cz \
--cc=soc@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).