From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Tudor.Ambarus@microchip.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, Nicolas.Ferre@microchip.com,
alexandre.belloni@bootlin.com, Claudiu.Beznea@microchip.com,
Lars.Povlsen@microchip.com, Steen.Hegelund@microchip.com,
UNGLinuxDriver@microchip.com, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] ARM: dts: at91: align SPI NOR node name with dtschema
Date: Tue, 12 Apr 2022 12:43:44 +0200 [thread overview]
Message-ID: <32b3f189-d284-274b-f238-0e09dc58f8e4@linaro.org> (raw)
In-Reply-To: <0c0b19ac-9047-509b-1112-cb25fa00ae22@microchip.com>
On 12/04/2022 12:41, Tudor.Ambarus@microchip.com wrote:
>>>
>
> I've just noticed that there are other node names that can be fixed,
> if you feel like resubmitting:
> arch/arm/boot/dts/at91rm9200ek.dts: mtd_dataflash@0 {
> arch/arm/boot/dts/at91rm9200ek.dts: nor_flash@10000000 {
> arch/arm/boot/dts/at91sam9260ek.dts: mtd_dataflash@1 {
> arch/arm/boot/dts/at91sam9261ek.dts: mtd_dataflash@0 {
> arch/arm/boot/dts/at91sam9263ek.dts: mtd_dataflash@0 {
> arch/arm/boot/dts/at91sam9g20ek_common.dtsi: mtd_dataflash@1 {
> arch/arm/boot/dts/at91sam9m10g45ek.dts: mtd_dataflash@0 {
> arch/arm/boot/dts/at91sam9rlek.dts: mtd_dataflash@0 {
These are not the same bindings, but I can fix them as well (separate
patch I guess?).
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-04-12 11:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 14:32 [PATCH 1/2] ARM: dts: at91: align SPI NOR node name with dtschema Krzysztof Kozlowski
2022-04-07 14:32 ` [PATCH 2/2] arm64: dts: microchip: " Krzysztof Kozlowski
2022-04-12 10:43 ` Tudor.Ambarus
2022-04-20 9:10 ` (subset) " Krzysztof Kozlowski
2022-04-12 10:32 ` [PATCH 1/2] ARM: dts: at91: " Tudor.Ambarus
2022-04-12 10:41 ` Tudor.Ambarus
2022-04-12 10:43 ` Krzysztof Kozlowski [this message]
2022-04-13 9:21 ` Nicolas Ferre
2022-04-13 9:33 ` 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=32b3f189-d284-274b-f238-0e09dc58f8e4@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=Claudiu.Beznea@microchip.com \
--cc=Lars.Povlsen@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=Steen.Hegelund@microchip.com \
--cc=Tudor.Ambarus@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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).