linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
To: Jisheng Zhang <jszhang@marvell.com>,
	robh+dt@kernel.org, mark.rutland@arm.com, linux@armlinux.org.uk
Cc: 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: Wed, 28 Sep 2016 21:40:21 +0200	[thread overview]
Message-ID: <57EC1CA5.2030102@gmail.com> (raw)
In-Reply-To: <20160906084013.2887-1-jszhang@marvell.com>

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.

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(-)
>

  parent reply	other threads:[~2016-09-28 19:40 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 ` Sebastian Hesselbarth [this message]
2016-09-29 10:44   ` [PATCH 00/10] ARM: dts: berlin: fix dtc warnings Jisheng Zhang

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=57EC1CA5.2030102@gmail.com \
    --to=sebastian.hesselbarth@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jszhang@marvell.com \
    --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 \
    /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).