From: Michael Walle <michael@walle.cc>
To: Kavyasree.Kotagiri@microchip.com
Cc: Tudor.Ambarus@microchip.com, Manohar.Puri@microchip.com,
Nicolas.Ferre@microchip.com, UNGLinuxDriver@microchip.com,
alexandre.belloni@bootlin.com, arnd@arndb.de,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, olof@lixom.net, robh+dt@kernel.org,
soc@kernel.org
Subject: Re: [PATCH v4] ARM: dts: add DT for lan966 SoC and 2-port board pcb8291
Date: Thu, 10 Feb 2022 14:33:57 +0100 [thread overview]
Message-ID: <51e33e946b096c903b0cacb5681fc6f1@walle.cc> (raw)
In-Reply-To: <CO1PR11MB4865B76B9B26EE938E3E67CE922F9@CO1PR11MB4865.namprd11.prod.outlook.com>
Am 2022-02-10 14:02, schrieb Kavyasree.Kotagiri@microchip.com:
>> EXTERNAL EMAIL: Do not click links or open attachments unless you know
>> the
>> content is safe
>>
>> Hi,
>>
>> > arch/arm/boot/dts/Makefile | 2 +
>> > arch/arm/boot/dts/lan966x.dtsi | 237 ++++++++++++++++++++++++++
>> > arch/arm/boot/dts/lan966x_pcb8291.dts | 61 +++++++
>>
>> Please rename this to lan966x-pcb8921.dts. All (most?) of the device
>> tree files use the dash as a seperator between the SoC and the board.
>>
> Ok, I will change in my v6.
> Please have a look at my v5 patch where I already addressed all the
> node naming changes.
My comments besides the renaming still apply.
-michael
next prev parent reply other threads:[~2022-02-10 13:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 11:13 [PATCH v4] ARM: dts: add DT for lan966 SoC and 2-port board pcb8291 Kavyasree Kotagiri
2022-02-09 12:32 ` Tudor.Ambarus
2022-02-10 12:37 ` Michael Walle
2022-02-10 13:02 ` Kavyasree.Kotagiri
2022-02-10 13:33 ` Michael Walle [this message]
2022-02-18 10:55 ` Kavyasree.Kotagiri
2022-02-09 18:46 ` Michael Walle
2022-02-10 9:40 ` Kavyasree.Kotagiri
2022-02-10 9:50 ` Michael Walle
2022-02-10 11:52 ` Kavyasree.Kotagiri
2022-02-10 12:05 ` Michael Walle
2022-02-18 12:28 ` Kavyasree.Kotagiri
2022-02-18 12:32 ` Michael Walle
2022-02-21 5:44 ` Kavyasree.Kotagiri
2022-02-21 7:28 ` Michael Walle
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=51e33e946b096c903b0cacb5681fc6f1@walle.cc \
--to=michael@walle.cc \
--cc=Kavyasree.Kotagiri@microchip.com \
--cc=Manohar.Puri@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=Tudor.Ambarus@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=soc@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).