From: David Gibson <david@gibson.dropbear.id.au>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Stephen Warren <swarren@wwwdotorg.org>,
Scott Wood <scottwood@freescale.com>,
Michal Marek <mmarek@suse.cz>,
devicetree-discuss@lists.ozlabs.org,
Stephen Warren <swarren@nvidia.com>,
linux-kernel@vger.kernel.org
Subject: Re: dtc: import latest upstream dtc
Date: Sun, 14 Oct 2012 10:16:41 +1000 [thread overview]
Message-ID: <20121014001641.GI4640@truffula.fritz.box> (raw)
In-Reply-To: <3C5DD611-6F36-4D13-9A88-377A8E30AAA5@kernel.crashing.org>
On Sat, Oct 13, 2012 at 03:42:35PM +0200, Segher Boessenkool wrote:
> >Oh, that's strange. I'm pretty sure I've used -x assembler when I've
> >experimented with using cpp on dts manually before, and it seems to
> >have worked.
>
> Maybe you used "-x assembler-with-cpp"? That should work better ;-)
> Or just use the "-traditional-cpp" option, i.e. "gcc -E
> -traditional-cpp".
Ah, yes, assembler-with-cpp, that's the one I used.
> > Note that IIRC with gcc cpp, -x assembler also means
> >that # won't be handled as a cpp directive except in column 0 which is
> >also an advantage for us, although no longer essential with your
> >escaping support. Not all cpps have an equivalent option, though.
>
> This is how the traditional C pre-processor behaves. I don't think
> this is exactly what matters for DTS, or does it ever happen that
> you have a # preceded only by whitespace?
Uh.. pretty much whenever you define a #address-cells or #size-cells
property. At least until Stephen's patch to allow escaping that.
> The # and ## stringification
> and token pasting ops will of course bite you with the ISO C pre-processor,
> indeed.
>
>
> Segher
>
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
next prev parent reply other threads:[~2012-10-14 7:44 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-28 21:25 [PATCH] " Stephen Warren
2012-09-29 21:06 ` Jon Loeliger
2012-10-01 16:09 ` Rob Herring
2012-10-01 16:13 ` Stephen Warren
2012-10-01 17:56 ` Rob Herring
2012-10-01 18:33 ` Stephen Warren
2012-10-01 18:39 ` Jon Loeliger
2012-10-09 21:16 ` Stephen Warren
2012-10-09 23:20 ` Mitch Bradley
2012-10-10 0:04 ` Scott Wood
2012-10-10 4:43 ` Warner Losh
2012-10-10 7:24 ` David Gibson
2012-10-10 14:41 ` Warner Losh
2012-10-10 23:06 ` David Gibson
2012-10-10 15:16 ` Stephen Warren
2012-10-10 15:33 ` Rob Herring
2012-10-10 16:19 ` Stephen Warren
2012-10-10 17:18 ` Rob Herring
2012-10-10 18:42 ` Stephen Warren
2012-10-10 23:16 ` David Gibson
2012-10-11 1:42 ` Mitch Bradley
2012-10-11 5:11 ` David Gibson
2012-10-10 23:09 ` David Gibson
2012-10-10 15:15 ` Stephen Warren
2012-10-10 16:09 ` Scott Wood
2012-10-10 16:22 ` Stephen Warren
2012-10-10 23:18 ` David Gibson
2012-10-12 17:24 ` Stephen Warren
2012-10-13 6:24 ` David Gibson
2012-10-13 13:42 ` Segher Boessenkool
2012-10-14 0:16 ` David Gibson [this message]
2012-10-10 17:09 ` Rob Herring
2012-10-10 18:23 ` Mitch Bradley
2012-10-10 18:45 ` Stephen Warren
2012-10-10 18:56 ` Mitch Bradley
2012-10-11 0:14 ` David Gibson
2012-10-10 23:54 ` David Gibson
2012-10-10 18:40 ` Stephen Warren
2012-10-10 18:52 ` Mitch Bradley
2012-10-01 18:02 ` Jon Loeliger
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=20121014001641.GI4640@truffula.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=scottwood@freescale.com \
--cc=segher@kernel.crashing.org \
--cc=swarren@nvidia.com \
--cc=swarren@wwwdotorg.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®