From: Javier Martinez Canillas <javier@osg.samsung.com>
To: linux-kernel@vger.kernel.org
Cc: devicetree@vger.kernel.org, Heiko Stuebner <heiko@sntech.de>,
linux-rockchip@lists.infradead.org,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-arm-kernel@lists.infradead.org,
Javier Martinez Canillas <javier@osg.samsung.com>
Subject: [PATCH 5/8] ARM: dts: rockchip: Add missing unit name to memory nodes in rk3036 boards
Date: Fri, 9 Sep 2016 10:01:06 -0400 [thread overview]
Message-ID: <1473429669-6185-6-git-send-email-javier@osg.samsung.com> (raw)
In-Reply-To: <1473429669-6185-1-git-send-email-javier@osg.samsung.com>
This patch fixes the following DTC warnings:
"Node /memory has a reg or ranges property, but no unit name"
Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com>
---
arch/arm/boot/dts/rk3036-evb.dts | 2 +-
arch/arm/boot/dts/rk3036-kylin.dts | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/rk3036-evb.dts b/arch/arm/boot/dts/rk3036-evb.dts
index 8db9e9b197a2..2f5f15524fba 100644
--- a/arch/arm/boot/dts/rk3036-evb.dts
+++ b/arch/arm/boot/dts/rk3036-evb.dts
@@ -46,7 +46,7 @@
model = "Rockchip RK3036 Evaluation board";
compatible = "rockchip,rk3036-evb", "rockchip,rk3036";
- memory {
+ memory@60000000 {
device_type = "memory";
reg = <0x60000000 0x40000000>;
};
diff --git a/arch/arm/boot/dts/rk3036-kylin.dts b/arch/arm/boot/dts/rk3036-kylin.dts
index 1df1557a46c3..3de958ec29c0 100644
--- a/arch/arm/boot/dts/rk3036-kylin.dts
+++ b/arch/arm/boot/dts/rk3036-kylin.dts
@@ -46,7 +46,7 @@
model = "Rockchip RK3036 KylinBoard";
compatible = "rockchip,rk3036-kylin", "rockchip,rk3036";
- memory {
+ memory@60000000 {
device_type = "memory";
reg = <0x60000000 0x20000000>;
};
--
2.7.4
next prev parent reply other threads:[~2016-09-09 14:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-09 14:01 [PATCH 0/8] ARM: dts: rockchip: Remove skeleton.dtsi usage and fix memory node DTC warnings Javier Martinez Canillas
2016-09-09 14:01 ` [PATCH 1/8] ARM: dts: rockchip: Remove skeleton.dtsi inclusion in rk3036.dtsi Javier Martinez Canillas
2016-09-09 14:01 ` [PATCH 3/8] ARM: dts: rockchip: Remove skeleton.dtsi inclusion in rk3288.dtsi Javier Martinez Canillas
2016-09-09 14:01 ` [PATCH 4/8] ARM: dts: rockchip: Remove skeleton.dtsi inclusion in rk3xxx.dtsi Javier Martinez Canillas
2016-09-09 14:01 ` Javier Martinez Canillas [this message]
[not found] ` <1473429669-6185-1-git-send-email-javier-JPH+aEBZ4P+UEJcrhfAQsw@public.gmane.org>
2016-09-09 14:01 ` [PATCH 2/8] ARM: dts: rockchip: Remove skeleton.dtsi inclusion in rk322x.dtsi Javier Martinez Canillas
2016-09-09 14:01 ` [PATCH 6/8] ARM: dts: rockchip: Add missing unit name to memory nodes in rk322x boards Javier Martinez Canillas
2016-09-10 21:51 ` [PATCH 0/8] ARM: dts: rockchip: Remove skeleton.dtsi usage and fix memory node DTC warnings Heiko Stuebner
2016-09-09 14:01 ` [PATCH 7/8] ARM: dts: rockchip: Add missing unit name to memory nodes in rk3288 boards Javier Martinez Canillas
2016-09-09 14:01 ` [PATCH 8/8] ARM: dts: rockchip: Add missing unit name to memory nodes in rk3xxx boards Javier Martinez Canillas
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=1473429669-6185-6-git-send-email-javier@osg.samsung.com \
--to=javier@osg.samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--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