From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Michael Walle <michael@walle.cc>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
UNGLinuxDriver@microchip.com, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-mips@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] MIPS: mscc: jaguar2: rename pinctrl nodes
Date: Wed, 27 Apr 2022 11:00:50 +0200 [thread overview]
Message-ID: <20220427090050.GC8404@alpha.franken.de> (raw)
In-Reply-To: <20220420195018.3417053-1-michael@walle.cc>
On Wed, Apr 20, 2022 at 09:50:16PM +0200, Michael Walle wrote:
> The pinctrl device tree binding will be converted to YAML format. Rename
> the pin nodes so they end with "-pins" to match the schema.
>
> Signed-off-by: Michael Walle <michael@walle.cc>
> ---
> The YAML conversion patch is alread in
> https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git/log/?h=devel
>
> arch/mips/boot/dts/mscc/jaguar2_pcb110.dts | 10 +++++-----
> arch/mips/boot/dts/mscc/jaguar2_pcb111.dts | 10 +++++-----
> arch/mips/boot/dts/mscc/jaguar2_pcb118.dts | 6 +++---
> 3 files changed, 13 insertions(+), 13 deletions(-)
series 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:[~2022-04-27 9:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 19:50 [PATCH 1/3] MIPS: mscc: jaguar2: rename pinctrl nodes Michael Walle
2022-04-20 19:50 ` [PATCH 2/3] MIPS: mscc: ocelot: " Michael Walle
2022-04-20 19:50 ` [PATCH 3/3] MIPS: mscc: serval: " Michael Walle
2022-04-27 9:00 ` 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=20220427090050.GC8404@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=michael@walle.cc \
--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).