From: Jisheng Zhang <jszhang@marvell.com>
To: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Cc: <robh+dt@kernel.org>, <mark.rutland@arm.com>,
<linux@armlinux.org.uk>, <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 00/10] ARM: dts: berlin: fix dtc warnings
Date: Thu, 29 Sep 2016 18:44:12 +0800 [thread overview]
Message-ID: <20160929184412.7c535749@xhacker> (raw)
In-Reply-To: <57EC1CA5.2030102@gmail.com>
Hi Sebastian,
On Wed, 28 Sep 2016 21:40:21 +0200 Sebastian Hesselbarth wrote:
> On 06.09.2016 10:40, Jisheng Zhang wrote:
> > This is a clean up series to fix berlin arm platforms dtc warnings.
> > Firstly we remove skeleton.dtsi inclusion. Then add missing unit name
> > of /soc node and /memory node. Lastly, we fix regulators' name
> >
> > Jisheng Zhang (10):
> > ARM: dts: berlin2q: Remove skeleton.dtsi inclusion
> > ARM: dts: berlin2cd: Remove skeleton.dtsi inclusion
> > ARM: dts: berlin2: Remove skeleton.dtsi inclusion
> > ARM: dts: berlin2q: Add missing unit name to /soc node
> > ARM: dts: berlin2cd: Add missing unit name to /soc node
> > ARM: dts: berlin2: Add missing unit name to /soc node
> > ARM: dts: berlin2q-marvell-dmp: add missing unit name to /memory node
> > ARM: dts: chromecast: add missing unit name to /memory node
>
> Jisheng,
>
> Applied the 8 patches above.
>
> > ARM: dts: sony-nsz-gs7: add missing unit name to /memory node
>
> I didn't receive this one and could not find it online.
> I recreated the patch by using the chromecast patch above, so
> applied.
>
> > ARM: dts: berlin2q-marvell-dmp: fix regulators' name
>
> I have no clue what it should be fixed to.
DTC will complain with W=1:
Warning (unit_address_vs_reg): Node /regulators/regulator@0 has a unit
name, but no reg property
This patch tries to fix that warning.
Thanks,
Jisheng
>
> Sebastian
>
> > arch/arm/boot/dts/berlin2-sony-nsz-gs7.dts | 2 +-
> > arch/arm/boot/dts/berlin2.dtsi | 5 +++--
> > arch/arm/boot/dts/berlin2cd-google-chromecast.dts | 2 +-
> > arch/arm/boot/dts/berlin2cd.dtsi | 5 +++--
> > arch/arm/boot/dts/berlin2q-marvell-dmp.dts | 12 ++++++------
> > arch/arm/boot/dts/berlin2q.dtsi | 6 +++---
> > 6 files changed, 17 insertions(+), 15 deletions(-)
> >
>
prev parent reply other threads:[~2016-09-29 10:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 8:40 [PATCH 00/10] ARM: dts: berlin: fix dtc warnings Jisheng Zhang
2016-09-06 8:40 ` [PATCH 01/10] ARM: dts: berlin2q: Remove skeleton.dtsi inclusion Jisheng Zhang
2016-09-06 8:40 ` [PATCH 02/10] ARM: dts: berlin2cd: " Jisheng Zhang
2016-09-06 8:40 ` [PATCH 03/10] ARM: dts: berlin2: " Jisheng Zhang
2016-09-06 8:40 ` [PATCH 04/10] ARM: dts: berlin2q: Add missing unit name to /soc node Jisheng Zhang
2016-09-06 8:40 ` [PATCH 05/10] ARM: dts: berlin2cd: " Jisheng Zhang
2016-09-06 8:40 ` [PATCH 06/10] ARM: dts: berlin2: " Jisheng Zhang
2016-09-06 8:40 ` [PATCH 07/10] ARM: dts: berlin2q-marvell-dmp: add missing unit name to /memory node Jisheng Zhang
2016-09-06 8:40 ` [PATCH 08/10] ARM: dts: chromecast: " Jisheng Zhang
2016-09-28 19:40 ` [PATCH 00/10] ARM: dts: berlin: fix dtc warnings Sebastian Hesselbarth
2016-09-29 10:44 ` Jisheng Zhang [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=20160929184412.7c535749@xhacker \
--to=jszhang@marvell.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=robh+dt@kernel.org \
--cc=sebastian.hesselbarth@gmail.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).