devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frank Rowand <frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: "devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] scripts/dtc: update dtx_diff cpp and dts include paths to match build
Date: Sat, 16 Sep 2017 10:52:34 -0700	[thread overview]
Message-ID: <59BD64E2.9000605@gmail.com> (raw)
In-Reply-To: <CAL_JsqJDvhH7+4mHfvUhOnc9tsHw49P=+FjVtWCErNnKrH9-zA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On 09/15/17 15:42, Rob Herring wrote:
> On Fri, Sep 15, 2017 at 5:16 PM,  <frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>> From: Frank Rowand <frank.rowand-7U/KSKJipcs@public.gmane.org>
> 
> I feel like we just had the same subject. Can you make it more specific.

Yes, the previous one was pretty much the same words, but the one line
description is not an exact match.  I will come up with a more unique
subject.


>> Update dtx_diff include paths in the same manner as:
>> commit b12869a8d519 ("of: remove drivers/of/testcase-data from
>> include search path for CPP"), commit 5ffa2aed389c ("of: remove
>> arch/$(SRCARCH)/boot/dts from include search path for CPP"), and
>> commit 50f9ddaf64e1 ("of: search scripts/dtc/include-prefixes path
>> for both CPP and DTC").
> 
> We need a better way for this to stop happening besides me remembering
> in reviews...

Yep, me remembering in reviews.  Which I have.  :-)


> Perhaps a separate file of include paths that all tools can use?

I considered that with the very first version of dtx_diff.  At the time,
I expected changes to the include path to be very rare.  I still have
that expectation looking forward.

I considered having dtx_diff scrape the include paths out of Makefile.lib,
but that seemed fragile and kludgey.  I could create a shell script that
outputs the include paths,  Then Makefile.lib and dtx_diff could use
that script to get the include paths.


>> Remove proposed include path kernel/dts/, which was never implemented
>> for the dtb build.
>>
>> For the diff case, each source file is compiled separately.  For
>> each of those compiles, provide the location of the source file
>> as an include path, not the location of both source files.
>>
>> ---
>>
>> The referenced commits b12869a8d519, 5ffa2aed389c, 50f9ddaf64e1
>> are in v4.14-rc1.  No stable kernels need this patch.
>>
>>  scripts/dtc/dtx_diff |   22 +++++++++-------------
>>  1 file changed, 9 insertions(+), 13 deletions(-)
>>
>> Signed-off-by: Frank Rowand <frank.rowand-7U/KSKJipcs@public.gmane.org>
> 
> This is going to get dropped.
> 
> Rob

I am assuming the drop is because of the request to have a common
file for all tools to source for the include paths.  I'll re-spin
to implement that.

-Frank

--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2017-09-16 17:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-15 22:16 [PATCH] scripts/dtc: update dtx_diff cpp and dts include paths to match build frowand.list-Re5JQEeQqe8AvxtiuMwx3w
2017-09-15 22:42 ` Rob Herring
     [not found]   ` <CAL_JsqJDvhH7+4mHfvUhOnc9tsHw49P=+FjVtWCErNnKrH9-zA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-09-16 17:52     ` Frank Rowand [this message]
2017-09-18 15:01       ` 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=59BD64E2.9000605@gmail.com \
    --to=frowand.list-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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).