From: Frank Rowand <frowand.list@gmail.com>
To: Rob Herring <robh@kernel.org>, devicetree@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] of: unittest: let dtc generate __local_fixups__
Date: Thu, 16 Nov 2017 13:34:15 -0500 [thread overview]
Message-ID: <fb992198-d55c-0d06-3f19-0444d0c292d3@gmail.com> (raw)
In-Reply-To: <20171116180545.12322-1-robh@kernel.org>
On 11/16/17 13:05, Rob Herring wrote:
> Remove the manually added __local_fixups__ because dtc can now generate
> them. This also fixes a new warning in the process:
>
> drivers/of/unittest-data/testcases.dtb: Warning (interrupts_extended_property): Could not get phandle node for /__local_fixups__/testcase-data/interrupts/interrupts-extended0:interrupts-extended(cell 3)
>
> Signed-off-by: Rob Herring <robh@kernel.org>
> ---
> drivers/of/unittest-data/testcases.dts | 56 ++--------------------------------
> 1 file changed, 2 insertions(+), 54 deletions(-)
>
> diff --git a/drivers/of/unittest-data/testcases.dts b/drivers/of/unittest-data/testcases.dts
> index 12f7c3d649c8..ac616ad18ea6 100644
> --- a/drivers/of/unittest-data/testcases.dts
> +++ b/drivers/of/unittest-data/testcases.dts
> @@ -1,4 +1,6 @@
> /dts-v1/;
> +/plugin/;
> +
> / {
> testcase-data {
> changeset {
> @@ -23,57 +25,3 @@
> * The format of this data may be subject to change. For the time being consider
> * this a kernel-internal data format.
> */
> -/ { __local_fixups__ {
> - testcase-data {
> - phandle-tests {
> - consumer-a {
< snip >
You should also delete the comment immediately above that describes the removed lines.
next prev parent reply other threads:[~2017-11-16 18:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-16 18:05 Rob Herring
2017-11-16 18:05 ` [PATCH 2/2] of: unittest: disable interrupts_property warning Rob Herring
2017-11-16 18:34 ` Frank Rowand [this message]
2017-11-16 18:42 ` [PATCH 1/2] of: unittest: let dtc generate __local_fixups__ Rob Herring
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=fb992198-d55c-0d06-3f19-0444d0c292d3@gmail.com \
--to=frowand.list@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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
all inboxes | Powered by JetHome®