soc.lore.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@kernel.org>
To: Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
	Chanho Park <chanho61.park@samsung.com>
Cc: soc@kernel.org, Arnd Bergmann <arnd@arndb.de>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 2/2] arm64: exynos: fix cpu unit name warnings
Date: Wed, 13 Oct 2021 16:37:44 +0200	[thread overview]
Message-ID: <20211013143810.2101838-2-arnd@kernel.org> (raw)
Message-ID: <20211013143744.caxMt32pqbKFMbKd_XpISelcE6Zu7zxKLuHeNLAs2e0@z> (raw)
In-Reply-To: <20211013143810.2101838-1-arnd@kernel.org>

From: Arnd Bergmann <arnd@arndb.de>

dtc started warning about some of the CPU addresses:

arch/arm64/boot/dts/exynos/exynosautov9.dtsi:78.20-83.5: Warning (unit_address_format): /cpus/cpu@000000: unit name should not have leading 0s
arch/arm64/boot/dts/exynos/exynosautov9.dtsi:85.20-90.5: Warning (unit_address_format): /cpus/cpu@000100: unit name should not have leading 0s
arch/arm64/boot/dts/exynos/exynosautov9.dtsi:92.20-97.5: Warning (unit_address_format): /cpus/cpu@000200: unit name should not have leading 0s
arch/arm64/boot/dts/exynos/exynosautov9.dtsi:99.20-104.5: Warning (unit_address_format): /cpus/cpu@000300: unit name should not have leading 0s

Remove the leading zeroes.

Fixes: f695b3f4c45d ("arm64: dts: exynos: add initial support for exynosautov9 SoC")
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
---
 arch/arm64/boot/dts/exynos/exynosautov9.dtsi | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/arch/arm64/boot/dts/exynos/exynosautov9.dtsi b/arch/arm64/boot/dts/exynos/exynosautov9.dtsi
index 1dd1d73a52b8..284a7adb474a 100644
--- a/arch/arm64/boot/dts/exynos/exynosautov9.dtsi
+++ b/arch/arm64/boot/dts/exynos/exynosautov9.dtsi
@@ -75,28 +75,28 @@ core3 {
 			};
 		};
 
-		cpu0: cpu@000000 {
+		cpu0: cpu@0 {
 			device_type = "cpu";
 			compatible = "arm,cortex-a76";
 			reg = <0x0>;
 			enable-method = "psci";
 		};
 
-		cpu1: cpu@000100 {
+		cpu1: cpu@100 {
 			device_type = "cpu";
 			compatible = "arm,cortex-a76";
 			reg = <0x100>;
 			enable-method = "psci";
 		};
 
-		cpu2: cpu@000200 {
+		cpu2: cpu@200 {
 			device_type = "cpu";
 			compatible = "arm,cortex-a76";
 			reg = <0x200>;
 			enable-method = "psci";
 		};
 
-		cpu3: cpu@000300 {
+		cpu3: cpu@300 {
 			device_type = "cpu";
 			compatible = "arm,cortex-a76";
 			reg = <0x300>;
-- 
2.29.2


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-10-13 14:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20211013143743.we1yI8NZ9sPL5u79YVoSyliKHyEpm-YCM0UT3Y2guTE@z>
2021-10-13 14:37 ` [PATCH 1/2] ARM: versatile: remove leading 0 on unit address Arnd Bergmann
     [not found]   ` <20211013143744.caxMt32pqbKFMbKd_XpISelcE6Zu7zxKLuHeNLAs2e0@z>
2021-10-13 14:37     ` Arnd Bergmann [this message]
     [not found]       ` <20211013150104.4s1xN55vWckFnvJmR4cfTYN2TtVmqm-GaFHs4zSvPYM@z>
2021-10-13 15:01         ` [PATCH 2/2] arm64: exynos: fix cpu unit name warnings Krzysztof Kozlowski
2021-10-13 15:01           ` Krzysztof Kozlowski
     [not found]           ` <20211013151239.Z1ZA-ZTBDUJGMgDoSwXKjKspBW8V5AHquP5jVIRFJFA@z>
2021-10-13 15:12             ` Arnd Bergmann
     [not found]   ` <20211013234314.W5p7gfBueySxPRt8Fd8B8o35myHIxRU4SNzeB95W8a8@z>
2021-10-13 23:43     ` [PATCH 1/2] ARM: versatile: remove leading 0 on unit address Linus Walleij
2021-10-13 23:43       ` Linus Walleij
     [not found]   ` <20211014005322.UKmTWDI2VngfYgBKGmJObzYakZMzNfpqGSao9HCsHsw@z>
2021-10-14  0:53     ` Rob Herring
2021-10-21 20:48       ` Arnd Bergmann
2021-10-21 20:48         ` Arnd Bergmann
2021-10-21 21:10         ` Rob Herring
2021-10-21 21:10           ` Rob Herring
2021-10-24 23:16           ` Linus Walleij
2021-10-24 23:16             ` Linus Walleij
2021-10-24 23:16             ` Linus Walleij

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=20211013143810.2101838-2-arnd@kernel.org \
    --to=arnd@kernel.org \
    --cc=arnd@arndb.de \
    --cc=chanho61.park@samsung.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski@canonical.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --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).