From: Michael Walle <michael@walle.cc>
To: Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
Lars Povlsen <lars.povlsen@microchip.com>,
Steen Hegelund <Steen.Hegelund@microchip.com>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Gregory CLEMENT <gregory.clement@bootlin.com>,
Paul Burton <paulburton@kernel.org>,
Quentin Schulz <quentin.schulz@bootlin.com>,
Antoine Tenart <atenart@kernel.org>,
Kavyasree Kotagiri <kavyasree.kotagiri@microchip.com>,
Nicolas Ferre <nicolas.ferre@microchip.com>
Cc: "David S . Miller" <davem@davemloft.net>,
UNGLinuxDriver@microchip.com, linux-gpio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-mips@vger.kernel.org
Subject: Re: [PATCH v3 0/6] pinctrl: ocelot: convert to YAML format
Date: Mon, 04 Apr 2022 13:45:48 +0200 [thread overview]
Message-ID: <41197a2523caf2a0b7b4835e9c911540@walle.cc> (raw)
In-Reply-To: <20220319204628.1759635-1-michael@walle.cc>
Am 2022-03-19 21:46, schrieb Michael Walle:
> Convert the pinctrl ocelot binding to the new YAML format. Pin
> configuration nodes should have a "-pins" postfix. But unfortunately,
> there are many device trees which don't follow this. First rename
> all these nodes and then convert the binding to the YAML format so
> that the validation will pass.
>
> Because there were no maintainers before and there is none in
> MAINTAINERS I added Alexandre Belloni and Lars Povlsen, juding by
> the commits - to the binding as maintainers. Please tell me if you
> disagree.
Linus, can this go through your pinctrl tree because there is this
series which depends on it:
https://lore.kernel.org/linux-gpio/20220313154640.63813-1-michael@walle.cc/
-michael
next prev parent reply other threads:[~2022-04-04 11:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-19 20:46 [PATCH v3 0/6] pinctrl: ocelot: convert to YAML format Michael Walle
2022-03-19 20:46 ` [PATCH v3 1/6] MIPS: mscc: jaguar2: rename pinctrl nodes Michael Walle
2022-03-19 20:46 ` [PATCH v3 2/6] MIPS: mscc: ocelot: " Michael Walle
2022-03-19 20:46 ` [PATCH v3 3/6] MIPS: mscc: serval: " Michael Walle
2022-03-19 20:46 ` [PATCH v3 4/6] arm64: dts: sparx5: " Michael Walle
2023-05-17 12:23 ` (subset) " Krzysztof Kozlowski
2022-03-19 20:46 ` [PATCH v3 5/6] ARM: dts: lan966x: " Michael Walle
2022-05-17 14:36 ` Nicolas Ferre
2022-03-19 20:46 ` [PATCH v3 6/6] dt-bindings: pinctrl: convert ocelot-pinctrl to YAML format Michael Walle
2022-03-20 10:54 ` Krzysztof Kozlowski
2022-03-20 11:08 ` Michael Walle
2022-03-20 11:17 ` Krzysztof Kozlowski
2022-04-17 23:41 ` Linus Walleij
2022-04-18 8:16 ` Michael Walle
2022-04-18 8:19 ` Michael Walle
2022-04-18 11:13 ` Krzysztof Kozlowski
2022-04-18 12:04 ` Michael Walle
2022-04-19 22:33 ` Linus Walleij
2022-04-04 11:45 ` Michael Walle [this message]
2022-04-19 22:28 ` [PATCH v3 0/6] pinctrl: ocelot: convert " 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=41197a2523caf2a0b7b4835e9c911540@walle.cc \
--to=michael@walle.cc \
--cc=Steen.Hegelund@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=atenart@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=kavyasree.kotagiri@microchip.com \
--cc=krzysztof.kozlowski@canonical.com \
--cc=lars.povlsen@microchip.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=paulburton@kernel.org \
--cc=quentin.schulz@bootlin.com \
--cc=robh+dt@kernel.org \
--cc=tsbogend@alpha.franken.de \
/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).