From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Alexander Dahl <post@lespocky.de>
Cc: Rob Herring <robh+dt@kernel.org>,
Alexander Dahl <ada@thorsis.com>,
linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-amlogic@lists.infradead.org, linux-mips@vger.kernel.org,
James Hartley <james.hartley@sondrel.com>,
Rahul Bedarkar <rahulbedarkar89@gmail.com>
Subject: Re: [PATCH v8 5/5] MIPS: DTS: img: Fix schema warnings for pwm-leds
Date: Mon, 7 Dec 2020 11:32:21 +0100 [thread overview]
Message-ID: <20201207103221.GA15686@alpha.franken.de> (raw)
In-Reply-To: <20201128215353.3991-6-post@lespocky.de>
On Sat, Nov 28, 2020 at 10:53:53PM +0100, Alexander Dahl wrote:
> The node names for devices using the pwm-leds driver follow a certain
> naming scheme (now). Parent node name is not enforced, but recommended
> by DT project.
>
> Signed-off-by: Alexander Dahl <post@lespocky.de>
> ---
>
> Notes:
> v7 -> v8:
> * rebased on v5.10-rc1
>
> v6 -> v7:
> * added another explaining sentence to commit message
>
> v6:
> * added this patch to series
>
> arch/mips/boot/dts/img/pistachio_marduk.dts | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2020-12-07 10:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-28 21:53 [PATCH v8 0/5] leds: pwm: Make automatic labels work Alexander Dahl
2020-11-28 21:53 ` [PATCH v8 1/5] dt-bindings: mfd: Fix schema warnings for pwm-leds Alexander Dahl
2020-11-28 21:53 ` [PATCH v8 2/5] ARM: dts: berlin: " Alexander Dahl
2020-11-28 21:53 ` [PATCH v8 3/5] ARM: dts: stm32: " Alexander Dahl
2020-11-28 22:00 ` [Linux-stm32] " Ahmad Fatoum
2020-11-28 21:53 ` [PATCH v8 4/5] arm64: dts: meson: " Alexander Dahl
2020-11-28 21:53 ` [PATCH v8 5/5] MIPS: DTS: img: " Alexander Dahl
2020-12-07 10:32 ` Thomas Bogendoerfer [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=20201207103221.GA15686@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=ada@thorsis.com \
--cc=devicetree@vger.kernel.org \
--cc=james.hartley@sondrel.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=post@lespocky.de \
--cc=rahulbedarkar89@gmail.com \
--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).