From: Stephen Warren <swarren@wwwdotorg.org>
To: Rob Herring <robherring2@gmail.com>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
Michal Marek <mmarek@suse.cz>,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org,
David Gibson <david@gibson.dropbear.id.au>,
Jon Loeliger <jdl@jdl.com>,
Grant Likely <grant.likely@secretlab.ca>,
Scott Wood <scottwood@freescale.com>,
Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>,
Stephen Warren <swarren@nvidia.com>
Subject: Re: [PATCH V4 REPOST 2/2] kbuild: run the pre-processor on *.dts files
Date: Sat, 27 Oct 2012 20:10:13 -0600 [thread overview]
Message-ID: <508C9405.5030600@wwwdotorg.org> (raw)
In-Reply-To: <fb065651-fd9d-4435-9a61-884dcb1da8d0@email.android.com>
On 10/27/2012 07:06 PM, Rob Herring wrote:
> Mark Brown <broonie@opensource.wolfsonmicro.com> wrote:
>
> On Fri, Oct 26, 2012 at 02:57:50PM -0500, Rob Herring wrote:
>
> Like I said previously, I think we first need guidelines on what
> is and
> isn't acceptable use of C preprocessor in dts files.
>
>
> Didn't we already say that it was just the same rules as for things tht
> get included in .S files? Besides for plain .dts files (as opposed to
> .dtsi files) it seems like if people break things they get to keep all
> the pieces without disrupting other people too much.
>
>
> Yes, but can we document that. Also, I'd like others with more DT
> historical knowledge to weigh in.
OK. What's the appropriate file to document that in? I assume you're not
just looking for an explanation in the commit description?
next prev parent reply other threads:[~2012-10-28 2:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-26 19:29 [PATCH V4 REPOST 1/2] kbuild: centralize .dts->.dtb rule Stephen Warren
[not found] ` <1351279797-16450-1-git-send-email-swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-10-26 19:29 ` [PATCH V4 REPOST 2/2] kbuild: run the pre-processor on *.dts files Stephen Warren
2012-10-26 19:29 ` Stephen Warren
2012-10-26 19:57 ` Rob Herring
2012-10-27 22:06 ` Mark Brown
[not found] ` <20121027220638.GK4564-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2012-10-28 1:06 ` Rob Herring
2012-10-28 2:10 ` Stephen Warren [this message]
2012-10-28 7:24 ` [PATCH V4 REPOST 1/2] kbuild: centralize .dts->.dtb rule Sam Ravnborg
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=508C9405.5030600@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=david@gibson.dropbear.id.au \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=jdl@jdl.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=plagnioj@jcrosoft.com \
--cc=robherring2@gmail.com \
--cc=scottwood@freescale.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.