From: Stephen Warren <swarren@wwwdotorg.org>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Michal Marek <mmarek@suse.cz>,
Grant Likely <glikely@secretlab.ca>,
Srinivas KANDAGATLA <srinivas.kandagatla@st.com>,
devicetree-discuss@lists.ozlabs.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
linux-kernel@vger.kernel.org,
Scott Wood <scottwood@freescale.com>,
Stephen Warren <swarren@nvidia.com>,
Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [PATCH V8] kbuild: create a rule to run the pre-processor on *.dts files
Date: Mon, 11 Feb 2013 12:11:22 -0700 [thread overview]
Message-ID: <5119425A.1090802@wwwdotorg.org> (raw)
In-Reply-To: <51157F65.2050309@wwwdotorg.org>
On 02/08/2013 08:45 AM, Grant Likely wrote:
> On Tue, 5 Feb 2013 12:06:28 -0700, Stephen Warren <swarren@wwwdotorg.org> wrote:
>> Create cmd_dtc_cpp to run the C pre-processor on *.dts file before
>> passing them to dtc for final compilation. This allows the use of #define
>> and #include within the .dts file.
...
> I've applied this and was going to push it out, but I've just thought of
> a problem that could be a show stopper. ...
Grant, I notice this showed up in next-20130211 as:
22435f3 kbuild: create a rule to run the pre-processor on *.dts files
Was that intentional? I assumed you wanted me to rework this before
you'd apply it, rather than sending an incremental patch.
next prev parent reply other threads:[~2013-02-11 19:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-05 19:06 Stephen Warren
2013-02-08 14:45 ` Grant Likely
2013-02-08 17:18 ` Stephen Warren
2013-02-08 20:50 ` Grant Likely
2013-02-08 21:24 ` Rob Herring
2013-02-08 22:04 ` Grant Likely
2013-02-08 22:42 ` Stephen Warren
2013-02-11 19:11 ` Stephen Warren [this message]
2013-02-12 18:08 ` Grant Likely
2013-02-12 19:27 ` Stephen Warren
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=5119425A.1090802@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=glikely@secretlab.ca \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=sam@ravnborg.org \
--cc=scottwood@freescale.com \
--cc=srinivas.kandagatla@st.com \
--cc=swarren@nvidia.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
all inboxes | Powered by JetHome®