public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: arm@kernel.org, Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>, Chen-Yu Tsai <wens@csie.org>,
	linaro-kernel@lists.linaro.org,
	linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org,
	Rafael Wysocki <rjw@rjwysocki.net>,
	Krzysztof Kozlowski <krzk@kernel.org>,
	Masahiro Yamada <yamada.masahiro@socionext.com>,
	Rob Herring <robh@kernel.org>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V4 5/7] ARM: sun8i: Use - instead of @ for DT OPP entries
Date: Thu, 20 Apr 2017 10:02:02 +0200	[thread overview]
Message-ID: <20170420080202.olu2mhel6xtmnnjt@lukather> (raw)
In-Reply-To: <d13e447e9cc080d81c4f2db3bd5433506d3ef739.1492666725.git.viresh.kumar@linaro.org>

[-- Attachment #1: Type: text/plain, Size: 859 bytes --]

Hi,

On Thu, Apr 20, 2017 at 11:14:16AM +0530, Viresh Kumar wrote:
> 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.
> 
> 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>
> Acked-by: Maxime Ripard <maxime.ripard@free-electrons.com>
> Acked-by: Rob Herring <robh@kernel.org>

This patch doesn't apply, please make sure to base them on linux-next

Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

  reply	other threads:[~2017-04-20  8:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1492666725.git.viresh.kumar@linaro.org>
2017-04-20  5:44 ` [PATCH V4 1/7] PM / OPP: Use - instead of @ for DT entries Viresh Kumar
2017-04-20  5:44 ` [PATCH V4 2/7] ARM: TI: Use - instead of @ for DT OPP entries Viresh Kumar
2017-04-20  5:44 ` [PATCH V4 3/7] ARM: exynos: " Viresh Kumar
2017-04-20  5:44 ` [PATCH V4 4/7] ARM: pxa: " Viresh Kumar
     [not found] ` <cover.1492666725.git.viresh.kumar-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2017-04-20  5:44   ` [PATCH V4 5/7] ARM: sun8i: " Viresh Kumar
2017-04-20  8:02     ` Maxime Ripard [this message]
2017-04-20  9:29       ` Viresh Kumar
2017-04-20  5:44 ` [PATCH V4 6/7] ARM: uniphier: " Viresh Kumar
2017-04-20  5:44 ` [PATCH V4 7/7] ARM: ZTE: " Viresh Kumar

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=20170420080202.olu2mhel6xtmnnjt@lukather \
    --to=maxime.ripard@free-electrons.com \
    --cc=arm@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk@kernel.org \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=rjw@rjwysocki.net \
    --cc=robh+dt@kernel.org \
    --cc=robh@kernel.org \
    --cc=viresh.kumar@linaro.org \
    --cc=wens@csie.org \
    --cc=yamada.masahiro@socionext.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