From: emilio@elopez.com.ar (Emilio López)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 4/7] kbuild: always run gcc -E on *.dts, remove cmd_dtc_cpp
Date: Wed, 03 Apr 2013 21:02:31 -0300 [thread overview]
Message-ID: <515CC317.2000703@elopez.com.ar> (raw)
In-Reply-To: <1365032098-22825-4-git-send-email-swarren@wwwdotorg.org>
Hi Stephen,
El 03/04/13 20:34, Stephen Warren escribi?:
> From: Stephen Warren <swarren@nvidia.com>
>
> Replace cmd_dtc with cmd_dtc_cpp, and delete the latter.
>
> Previously, a special file extension (.dtsp) was required to trigger
> the C pre-processor to run on device tree files. This was ugly. Now that
> previous changes have enhanced cmd_dtc_cpp to collect dependency
> information from both gcc -E and dtc, we can transparently run the pre-
> processor on all device tree files, irrespective of whether they
>
I think a line got dropped on the commit description by mistake.
Regards,
Emilio
next prev parent reply other threads:[~2013-04-04 0:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-03 23:34 [PATCH V2 1/7] kbuild: create an "include chroot" for DT bindings Stephen Warren
2013-04-03 23:34 ` [PATCH V2 2/7] kbuild: fixdep: support concatenated dep files Stephen Warren
2013-04-03 23:34 ` [PATCH V2 3/7] kbuild: cmd_dtc_cpp: extract deps from both gcc -E and dtc Stephen Warren
2013-04-03 23:34 ` [PATCH V2 4/7] kbuild: always run gcc -E on *.dts, remove cmd_dtc_cpp Stephen Warren
2013-04-04 0:02 ` Emilio López [this message]
2013-04-04 16:41 ` Stephen Warren
2013-04-03 23:34 ` [PATCH V2 5/7] ARM: dt: add header to define GPIO flags Stephen Warren
2013-04-03 23:34 ` [PATCH V2 6/7] ARM: dt: add header to define IRQ flags Stephen Warren
2013-04-03 23:34 ` [PATCH V2 7/7] ARM: dt: create a DT header for the GIC Stephen Warren
2013-04-04 23:17 ` [PATCH V2 1/7] kbuild: create an "include chroot" for DT bindings Rob Herring
2013-04-05 1:01 ` Stephen Warren
2013-04-05 16:06 ` Rob Herring
2013-04-19 10:01 ` Grant Likely
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=515CC317.2000703@elopez.com.ar \
--to=emilio@elopez.com.ar \
--cc=linux-arm-kernel@lists.infradead.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).