From: Corentin Labbe <clabbe.montjoie@gmail.com>
To: robh+dt@kernel.org, mark.rutland@arm.com, linux@armlinux.org.uk,
maxime.ripard@free-electrons.com, wens@csie.org,
catalin.marinas@arm.com, will.deacon@arm.com
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Corentin Labbe <clabbe.montjoie@gmail.com>
Subject: [PATCH 06/12] ARM: dts: sun8i: orangepi-lite: Fix node with unit name and no reg property
Date: Thu, 21 Sep 2017 19:21:45 +0200 [thread overview]
Message-ID: <20170921172151.29779-7-clabbe.montjoie@gmail.com> (raw)
In-Reply-To: <20170921172151.29779-1-clabbe.montjoie@gmail.com>
This patch fix the warning "xxx has a unit name, but no reg property" by
removing "@0" from such node.
Signed-off-by: Corentin Labbe <clabbe.montjoie@gmail.com>
---
arch/arm/boot/dts/sun8i-h3-orangepi-lite.dts | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/arm/boot/dts/sun8i-h3-orangepi-lite.dts b/arch/arm/boot/dts/sun8i-h3-orangepi-lite.dts
index 9b47a0def740..a70a1daf4e2c 100644
--- a/arch/arm/boot/dts/sun8i-h3-orangepi-lite.dts
+++ b/arch/arm/boot/dts/sun8i-h3-orangepi-lite.dts
@@ -141,19 +141,19 @@
};
&pio {
- leds_opc: led_pins@0 {
+ leds_opc: led_pins {
pins = "PA15";
function = "gpio_out";
};
};
&r_pio {
- leds_r_opc: led_pins@0 {
+ leds_r_opc: led_pins {
pins = "PL10";
function = "gpio_out";
};
- sw_r_opc: key_pins@0 {
+ sw_r_opc: key_pins {
pins = "PL3";
function = "gpio_in";
};
--
2.13.5
next prev parent reply other threads:[~2017-09-21 17:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-21 17:21 [PATCH 00/12] ARM: dts: sunxi: Fix DT build warnings Corentin Labbe
2017-09-21 17:21 ` [PATCH 01/12] ARM: dts: sunxi: h3/h5: Fix simple-bus unit address format error Corentin Labbe
2017-09-21 17:21 ` [PATCH 02/12] ARM: dts: sunxi: h3/h5: Fix i2c2 register address Corentin Labbe
[not found] ` <20170921172151.29779-3-clabbe.montjoie-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-09-22 7:49 ` Maxime Ripard
[not found] ` <20170922074945.jzibcgromgbhggxy-ZC1Zs529Oq4@public.gmane.org>
2017-09-22 8:02 ` Corentin Labbe
2017-09-21 17:21 ` [PATCH 03/12] ARM: dts: sunxi: h3/h5: Fix node with unit name and no reg property Corentin Labbe
2017-09-21 17:21 ` [PATCH 04/12] ARM: dts: nanopi: " Corentin Labbe
2017-09-21 17:21 ` [PATCH 05/12] ARM: dts: orangepi2: " Corentin Labbe
2017-09-21 17:21 ` Corentin Labbe [this message]
[not found] ` <20170921172151.29779-1-clabbe.montjoie-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-09-21 17:21 ` [PATCH 07/12] ARM: dts: sun8i: orangepi one: " Corentin Labbe
2017-09-21 17:21 ` [PATCH 08/12] ARM: dts: sun8i: orangepipc: " Corentin Labbe
2017-09-21 17:21 ` [PATCH 09/12] ARM: dts: sun8i: orangepi-plus: " Corentin Labbe
2017-09-21 17:21 ` [PATCH 10/12] arm64: allwinner: a64: Fix simple-bus unit address format error Corentin Labbe
2017-09-21 17:21 ` [PATCH 11/12] arm64: allwinner: a64: Fix node with unit name and no reg property Corentin Labbe
2017-09-21 17:21 ` [PATCH 12/12] ARM: sun8i: a83t: Fix simple-bus unit address format error Corentin Labbe
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=20170921172151.29779-7-clabbe.montjoie@gmail.com \
--to=clabbe.montjoie@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@free-electrons.com \
--cc=robh+dt@kernel.org \
--cc=wens@csie.org \
--cc=will.deacon@arm.com \
/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).