From: <Tudor.Ambarus@microchip.com>
To: <Eugen.Hristev@microchip.com>, <u-boot@lists.denx.de>
Cc: <Claudiu.Beznea@microchip.com>, <Codrin.Ciubotariu@microchip.com>,
<Hari.PrasathGE@microchip.com>
Subject: Re: [PATCH 1/2] ARM: dts: at91: rename sama7g5ek.dts to at91-sama7g5ek.dts
Date: Mon, 7 Mar 2022 10:52:21 +0000 [thread overview]
Message-ID: <8a076b2e-c269-0ec1-6e2b-2f66de0ee1ca@microchip.com> (raw)
In-Reply-To: <20220307084239.2370181-1-eugen.hristev@microchip.com>
Hi, Eugen,
On 3/7/22 10:42, Eugen Hristev wrote:
> In Linux this DT file is named at91-sama7g5ek.dts. Rename it accordingly.
>
> Signed-off-by: Eugen Hristev <eugen.hristev@microchip.com>
> ---
> arch/arm/dts/Makefile | 2 +-
> arch/arm/dts/{sama7g5ek.dts => at91-sama7g5ek.dts} | 0
> configs/sama7g5ek_mmc1_defconfig | 2 +-
> configs/sama7g5ek_mmc_defconfig | 2 +-
> 4 files changed, 3 insertions(+), 3 deletions(-)
> rename arch/arm/dts/{sama7g5ek.dts => at91-sama7g5ek.dts} (100%)
I find the idea good, but you should update in other places too:
~/work/u-boot$ git grep sama7g5ek
arch/arm/dts/at91-sama7g5ek.dts: * sama7g5ek.dts - Device Tree file for SAMA7G5 EK
arch/arm/dts/sama7g5ek-u-boot.dtsi: * sama7g5ek-u-boot.dts - Device Tree file for SAMA7G5 SoC u-boot properties.
With these addressed:
Reviewed-by: Tudor Ambarus <tudor.ambarus@microchip.com>
prev parent reply other threads:[~2022-03-07 10:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 8:42 [PATCH 1/2] ARM: dts: at91: rename sama7g5ek.dts to at91-sama7g5ek.dts Eugen Hristev
2022-03-07 8:42 ` [PATCH 2/2] ARM: dts: at91: sama7g5/sama7g5ek: align with Linux DT Eugen Hristev
2022-03-07 11:05 ` Tudor.Ambarus
2022-03-07 11:27 ` Eugen.Hristev
2022-03-07 10:52 ` Tudor.Ambarus [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=8a076b2e-c269-0ec1-6e2b-2f66de0ee1ca@microchip.com \
--to=tudor.ambarus@microchip.com \
--cc=Claudiu.Beznea@microchip.com \
--cc=Codrin.Ciubotariu@microchip.com \
--cc=Eugen.Hristev@microchip.com \
--cc=Hari.PrasathGE@microchip.com \
--cc=u-boot@lists.denx.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