From: Viresh Kumar <viresh.kumar@linaro.org>
To: arm@kernel.org
Cc: linaro-kernel@lists.linaro.org,
linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org,
"Rafael Wysocki" <rjw@rjwysocki.net>,
"Viresh Kumar" <viresh.kumar@linaro.org>,
"Chanwoo Choi" <cw00.choi@samsung.com>,
"MyungJoo Ham" <myungjoo.ham@samsung.com>,
"Kyungmin Park" <kyungmin.park@samsung.com>,
"Kukjin Kim" <kgene@kernel.org>,
"Krzysztof Kozlowski" <krzk@kernel.org>,
"Javier Martinez Canillas" <javier@osg.samsung.com>,
"Viresh Kumar" <vireshk@kernel.org>, "Nishanth Menon" <nm@ti.com>,
"Stephen Boyd" <sboyd@codeaurora.org>,
"Benoît Cousson" <bcousson@baylibre.com>,
"Tony Lindgren" <tony@atomide.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"Daniel Mack" <daniel@zonque.org>,
"Haojian Zhuang" <haojian.zhuang@gmail.com>
Subject: [PATCH V5 0/7] PM / OPP: Use - instead of @ for DT entries
Date: Thu, 20 Apr 2017 16:25:04 +0530 [thread overview]
Message-ID: <cover.1492685450.git.viresh.kumar@linaro.org> (raw)
Compiling the DT file with W=1, DTC warns like follows:
Warning (unit_address_vs_reg): Node /opp_table0/opp@1000000000 has a
unit name, but no reg property
Fix this by replacing '@' with '-' as the OPP nodes will never have a
"reg" property.
This is rebased over arm-soc/for-next:
commit 6f714927c553 ("ARM: SoC: Document merges")
Platform maintainers shall apply patches touching their code.
V4->V5:
- Rebased on arm-soc/for-next. Couldn't do that on linux-next/master as
it still had the V3 patch via the PM tree (which will be dropped
today).
- Some more OPP entries got the update as they were present only in
next.
V3->V4:
- split it per platform
V2->V3:
- Rebased over 4.11-rc7 and fixed a merge conflict for sun8i.
--
Viresh
Viresh Kumar (7):
PM / OPP: Use - instead of @ for DT entries
ARM: TI: Use - instead of @ for DT OPP entries
ARM: exynos: Use - instead of @ for DT OPP entries
ARM: pxa: Use - instead of @ for DT OPP entries
ARM: sun8i: Use - instead of @ for DT OPP entries
ARM: uniphier: Use - instead of @ for DT OPP entries
ARM: ZTE: Use - instead of @ for DT OPP entries
.../devicetree/bindings/cpufreq/ti-cpufreq.txt | 20 +++----
.../devicetree/bindings/devfreq/exynos-bus.txt | 46 +++++++--------
Documentation/devicetree/bindings/opp/opp.txt | 38 ++++++-------
arch/arm/boot/dts/am335x-boneblack.dts | 2 +-
arch/arm/boot/dts/am33xx.dtsi | 20 +++----
arch/arm/boot/dts/am4372.dtsi | 10 ++--
arch/arm/boot/dts/dra7.dtsi | 4 +-
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/arm/boot/dts/pxa25x.dtsi | 8 +--
arch/arm/boot/dts/pxa27x.dtsi | 14 ++---
arch/arm/boot/dts/sun8i-a33-sinlinx-sina33.dts | 4 +-
arch/arm/boot/dts/sun8i-a33.dtsi | 30 +++++-----
arch/arm/boot/dts/uniphier-pro5.dtsi | 32 +++++------
arch/arm/boot/dts/uniphier-pxs2.dtsi | 16 +++---
arch/arm64/boot/dts/exynos/exynos5433-bus.dtsi | 48 ++++++++--------
arch/arm64/boot/dts/exynos/exynos5433.dtsi | 50 ++++++++--------
arch/arm64/boot/dts/socionext/uniphier-ld11.dtsi | 14 ++---
arch/arm64/boot/dts/socionext/uniphier-ld20.dtsi | 32 +++++------
arch/arm64/boot/dts/zte/zx296718.dtsi | 10 ++--
24 files changed, 321 insertions(+), 321 deletions(-)
--
2.12.0.432.g71c3a4f4ba37
next reply other threads:[~2017-04-20 10:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 10:55 Viresh Kumar [this message]
[not found] ` <cover.1492685450.git.viresh.kumar-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2017-04-20 10:55 ` [PATCH V5 1/7] PM / OPP: Use - instead of @ for DT entries Viresh Kumar
2017-04-20 10:55 ` [PATCH V5 5/7] ARM: sun8i: Use - instead of @ for DT OPP entries Viresh Kumar
2017-04-21 7:35 ` Maxime Ripard
2017-04-20 10:55 ` [PATCH V5 2/7] ARM: TI: " 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
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 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
[not found] ` <5534c08d8b452c8ce623d3e465603d94afd82ed4.1492685450.git.viresh.kumar-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
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=cover.1492685450.git.viresh.kumar@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=arm@kernel.org \
--cc=bcousson@baylibre.com \
--cc=cw00.choi@samsung.com \
--cc=daniel@zonque.org \
--cc=haojian.zhuang@gmail.com \
--cc=javier@osg.samsung.com \
--cc=kgene@kernel.org \
--cc=krzk@kernel.org \
--cc=kyungmin.park@samsung.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=myungjoo.ham@samsung.com \
--cc=nm@ti.com \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=tony@atomide.com \
--cc=vireshk@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).