public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V5 3/7] ARM: exynos: Use - instead of @ for DT OPP entries
Date: Fri, 21 Apr 2017 10:57:05 +0530	[thread overview]
Message-ID: <20170421052705.GA26900@vireshk-i7> (raw)
In-Reply-To: <20170420160930.halyszjunt4q2634@kozik-lap>

On 20-04-17, 18:09, Krzysztof Kozlowski wrote:
> On Thu, Apr 20, 2017 at 04:25:07PM +0530, Viresh Kumar wrote:
> > Compiling the DT file with W=1, DTC warns like follows:
> > 
> > Warning (unit_address_vs_reg): Node /opp_table0/opp at 1000000000 has a
> > unit name, but no reg property
> > 
> > Fix this by replacing '@' with '-' as the OPP nodes will never have a
> > "reg" property.
> > 
> > Reported-by: Krzysztof Kozlowski <krzk@kernel.org>
> > Reported-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> > Suggested-by: Mark Rutland <mark.rutland@arm.com>
> > Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> > Reviewed-by: Chanwoo Choi <cw00.choi@samsung.com>
> > Reviewed-by: Krzysztof Kozlowski <krzk@kernel.org>
> > Acked-by: Rob Herring <robh@kernel.org>
> > ---
> >  .../devicetree/bindings/devfreq/exynos-bus.txt     | 46 +++++++--------
> >  arch/arm/boot/dts/exynos3250.dtsi                  | 46 +++++++--------
> >  arch/arm/boot/dts/exynos4210.dtsi                  | 32 +++++------
> >  arch/arm/boot/dts/exynos4412-prime.dtsi            |  4 +-
> >  arch/arm/boot/dts/exynos4412.dtsi                  | 66 +++++++++++-----------
> >  arch/arm/boot/dts/exynos5420.dtsi                  | 40 ++++++-------
> >  arch/arm/boot/dts/exynos5800.dtsi                  | 56 +++++++++---------
> >  arch/arm64/boot/dts/exynos/exynos5433-bus.dtsi     | 48 ++++++++--------
> >  arch/arm64/boot/dts/exynos/exynos5433.dtsi         | 50 ++++++++--------
> >  9 files changed, 194 insertions(+), 194 deletions(-)
> 
> 
> Thanks, split ARM64 from ARM and applied (for v4.12). arm-soc keeps DTS
> separated between ARM architectures. Technically this should require a
> resend but we had way too many resends for this simple patch.

Bah! Will make sure to send separate patches from now on. Thanks.

-- 
viresh

  reply	other threads:[~2017-04-21  5:27 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-20 10:55 [PATCH V5 0/7] PM / OPP: Use - instead of @ for DT entries Viresh Kumar
2017-04-20 10:55 ` [PATCH V5 1/7] " Viresh Kumar
2017-04-20 10:55 ` [PATCH V5 2/7] ARM: TI: Use - instead of @ for DT OPP entries Viresh Kumar
2017-05-16 15:19   ` Tony Lindgren
2017-04-20 10:55 ` [PATCH V5 3/7] ARM: exynos: " Viresh Kumar
2017-04-20 16:09   ` Krzysztof Kozlowski
2017-04-21  5:27     ` Viresh Kumar [this message]
2017-04-24  8:30     ` Masahiro Yamada
2017-04-24  8:32       ` Krzysztof Kozlowski
2017-04-20 10:55 ` [PATCH V5 4/7] ARM: pxa: " Viresh Kumar
2017-04-20 20:14   ` Robert Jarzmik
2017-04-21  5:30     ` Viresh Kumar
2017-04-21 16:02       ` Robert Jarzmik
2017-04-22 19:29         ` Robert Jarzmik
2017-04-20 10:55 ` [PATCH V5 5/7] ARM: sun8i: " Viresh Kumar
2017-04-21  7:35   ` Maxime Ripard
2017-04-20 10:55 ` [PATCH V5 6/7] ARM: uniphier: " Viresh Kumar
2017-05-13 16:23   ` Masahiro Yamada
2017-04-20 10:55 ` [PATCH V5 7/7] ARM: ZTE: " Viresh Kumar
2017-05-03 13:42   ` Shawn Guo

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=20170421052705.GA26900@vireshk-i7 \
    --to=viresh.kumar@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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