mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: barebox@lists.infradead.org
Subject: Re: [Question] device-tree-rebasing include path
Date: Wed, 19 Aug 2015 16:36:26 +0200	[thread overview]
Message-ID: <20150819143626.GJ18700@pengutronix.de> (raw)
In-Reply-To: <CAK7LNAQ5jJLpkszp5iT65zfcaQsfPqqvk0U=p+cB+E+tqN-oEQ@mail.gmail.com>

Hi Masahiro,

On Mon, Aug 10, 2015 at 08:05:59AM +0900, Masahiro Yamada wrote:
> Hi Sascha,
> 
> I have a question about the include path
> of device-tree-rebasing.
> 
> 
> When I saw scripts/Makefile.lib, I noticed that
> "-I $(srctree)/dts/src" is included for pre-processor,
> whereas "-i $(srctree)/dts/src/$(SRCARCH)" for DTC-native.
> 
> The root of device-tree-rebasing is dts/src/ when we use '#include',
> but dts/src/$(SRCARCH) when we use '/include/'
> 
> 
> Is this intentional?

Nope, this is not intentional. Currently there is no user for /include/ for
something in dts/, so we could change this to be consistent without
breaking anything.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2015-08-19 14:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-09 23:05 Masahiro Yamada
2015-08-19 14:36 ` Sascha Hauer [this message]
2015-10-22  3:35   ` Masahiro Yamada

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=20150819143626.GJ18700@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.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