From: Krzysztof Kozlowski <krzk@kernel.org>
To: Michael Walle <michael@walle.cc>,
Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
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 v2 6/8] arm64: dts: sparx5: fix pinctrl node names
Date: Sat, 19 Mar 2022 15:34:09 +0100 [thread overview]
Message-ID: <570331fb-bffa-da11-c6e4-6e059e418a93@kernel.org> (raw)
In-Reply-To: <20220318202547.1650687-7-michael@walle.cc>
On 18/03/2022 21:25, Michael Walle wrote:
> The pinctrl device tree binding will be converted to YAML format. All
> the pin nodes should end with "-pins". Fix them.
>
> Fixes: ("arm64: dts: sparx5: Add i2c devices, i2c muxes")
Here and in all commits, there is no bug to be fixed. Please remove
"Fixes" and remove "fix" word from commit msg and commit subject,
because you trick stable-AUTOSEL to pick up this patch to stables. This
must not go to stables as you can break out of tree usages.
There is no bug and there is no fix.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-03-19 14:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-18 20:25 [PATCH v2 0/8] pinctrl: ocelot: convert to YAML format Michael Walle
2022-03-18 20:25 ` [PATCH v2 1/8] MIPS: mscc: jaguar2: fix pinctrl nodes Michael Walle
2022-03-18 20:25 ` [PATCH v2 2/8] MIPS: mscc: ocelot: fix MIIM1 pinctrl node name Michael Walle
2022-03-18 20:25 ` [PATCH v2 3/8] MIPS: mscc: ocelot: fix PHY interrupt " Michael Walle
2022-03-18 20:25 ` [PATCH v2 4/8] MIPS: mscc: ocelot: fix load/save GPIO pinctrl name Michael Walle
2022-03-19 14:32 ` Krzysztof Kozlowski
2022-03-18 20:25 ` [PATCH v2 5/8] MIPS: mscc: serval: fix pinctrl node names Michael Walle
2022-03-18 20:25 ` [PATCH v2 6/8] arm64: dts: sparx5: " Michael Walle
2022-03-19 14:34 ` Krzysztof Kozlowski [this message]
2022-03-18 20:25 ` [PATCH v2 7/8] ARM: dts: lan9662-pcb8291: fix pinctrl node name Michael Walle
2022-03-19 8:24 ` Sergei Shtylyov
2022-03-19 11:38 ` Michael Walle
2022-03-20 8:20 ` Sergei Shtylyov
2022-03-18 20:25 ` [PATCH v2 8/8] dt-bindings: pinctrl: convert ocelot-pinctrl to YAML format Michael Walle
2022-03-19 14:30 ` Krzysztof Kozlowski
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=570331fb-bffa-da11-c6e4-6e059e418a93@kernel.org \
--to=krzk@kernel.org \
--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=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=michael@walle.cc \
--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).