linux-kernel - Re: [PATCH V4 REPOST 2/2] kbuild: run the pre-processor on *.dts files

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <508C9405.5030600@wwwdotorg.org>
Date:	Sat, 27 Oct 2012 20:10:13 -0600
From:	Stephen Warren <swarren@...dotorg.org>
To:	Rob Herring <robherring2@...il.com>
CC:	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	Michal Marek <mmarek@...e.cz>, linux-arch@...r.kernel.org,
	linux-kernel@...r.kernel.org, devicetree-discuss@...ts.ozlabs.org,
	David Gibson <david@...son.dropbear.id.au>,
	Jon Loeliger <jdl@....com>,
	Grant Likely <grant.likely@...retlab.ca>,
	Scott Wood <scottwood@...escale.com>,
	Jean-Christophe PLAGNIOL-VILLARD <plagnioj@...osoft.com>,
	Stephen Warren <swarren@...dia.com>
Subject: Re: [PATCH V4 REPOST 2/2] kbuild: run the pre-processor on *.dts
 files

On 10/27/2012 07:06 PM, Rob Herring wrote:
> Mark Brown <broonie@...nsource.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?

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/