From: Aleksander Jan Bajkowski <olek2@wp.pl>
To: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
tsbogend@alpha.franken.de, olek2@wp.pl,
devicetree@vger.kernel.org, linux-mips@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH] MIPS: dts: lantiq: rename dts files with soc name being the prefix
Date: Mon, 29 Aug 2022 20:37:17 +0200 [thread overview]
Message-ID: <20220829183717.4394-1-olek2@wp.pl> (raw)
Rename lantiq dts files with soc name being the prefix, so that the
board dts file can be located easily by soc name, and we also gain
the consistency of naming.
This patch is a preparation for the addition of dts for newer SoCs
(Lantiq ARX100, VRX200 and xRX330).
Signed-off-by: Aleksander Jan Bajkowski <olek2@wp.pl>
---
arch/mips/boot/dts/lantiq/Makefile | 2 +-
.../boot/dts/lantiq/{easy50712.dts => danube_easy50712.dts} | 0
2 files changed, 1 insertion(+), 1 deletion(-)
rename arch/mips/boot/dts/lantiq/{easy50712.dts => danube_easy50712.dts} (100%)
diff --git a/arch/mips/boot/dts/lantiq/Makefile b/arch/mips/boot/dts/lantiq/Makefile
index f5dfc06242b9..ae6e3e21ebeb 100644
--- a/arch/mips/boot/dts/lantiq/Makefile
+++ b/arch/mips/boot/dts/lantiq/Makefile
@@ -1,4 +1,4 @@
# SPDX-License-Identifier: GPL-2.0
-dtb-$(CONFIG_DT_EASY50712) += easy50712.dtb
+dtb-$(CONFIG_DT_EASY50712) += danube_easy50712.dtb
obj-$(CONFIG_BUILTIN_DTB) += $(addsuffix .o, $(dtb-y))
diff --git a/arch/mips/boot/dts/lantiq/easy50712.dts b/arch/mips/boot/dts/lantiq/danube_easy50712.dts
similarity index 100%
rename from arch/mips/boot/dts/lantiq/easy50712.dts
rename to arch/mips/boot/dts/lantiq/danube_easy50712.dts
--
2.30.2
next reply other threads:[~2022-08-29 18:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 18:37 Aleksander Jan Bajkowski [this message]
2022-09-26 9:08 ` [PATCH] MIPS: dts: lantiq: rename dts files with soc name being the prefix Thomas Bogendoerfer
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=20220829183717.4394-1-olek2@wp.pl \
--to=olek2@wp.pl \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--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).