All of lore.kernel.org
 help / color / mirror / Atom feed
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: Tue, 12 Feb 2013 12:27:57 -0700	[thread overview]
Message-ID: <511A97BD.9010707@wwwdotorg.org> (raw)
In-Reply-To: <20130212180805.556C93E1202@localhost>

On 02/12/2013 11:08 AM, Grant Likely wrote:
> On Mon, 11 Feb 2013 12:11:22 -0700, Stephen Warren <swarren@wwwdotorg.org> wrote:
>> 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.
> 
> Yes it was intentional. I sat on my hands w.r.t. this patch for long
> enough that I didn't want to delay it any longer. However, I still want
> a solution to the problem discussed above before it becomes a
> maintenance disaster.

OK, I'll send an incremental patch to adjust the include paths. It
should be soon; I think I have it written, but am distracted fixing up
Tegra clock driver issues etc.:-(

      reply	other threads:[~2013-02-12 19:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-05 19:06 [PATCH V8] kbuild: create a rule to run the pre-processor on *.dts files Stephen Warren
     [not found] ` <1360091188-24063-1-git-send-email-swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-02-08 14:45   ` Grant Likely
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
     [not found]             ` <5119425A.1090802-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-02-12 18:08               ` Grant Likely
2013-02-12 18:08                 ` Grant Likely
2013-02-12 19:27                 ` Stephen Warren [this message]

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=511A97BD.9010707@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.