linux-kernel - Re: [PATCH V8] kbuild: create a rule to 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>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 12 Feb 2013 12:27:57 -0700
From:	Stephen Warren <swarren@...dotorg.org>
To:	Grant Likely <grant.likely@...retlab.ca>
CC:	Michal Marek <mmarek@...e.cz>, Grant Likely <glikely@...retlab.ca>,
	Srinivas KANDAGATLA <srinivas.kandagatla@...com>,
	devicetree-discuss@...ts.ozlabs.org,
	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	linux-kernel@...r.kernel.org, Scott Wood <scottwood@...escale.com>,
	Stephen Warren <swarren@...dia.com>,
	Sam Ravnborg <sam@...nborg.org>
Subject: Re: [PATCH V8] kbuild: create a rule to run the pre-processor on
 *.dts files

On 02/12/2013 11:08 AM, Grant Likely wrote:
> On Mon, 11 Feb 2013 12:11:22 -0700, Stephen Warren <swarren@...dotorg.org> wrote:
>> On 02/08/2013 08:45 AM, Grant Likely wrote:
>>> On Tue,  5 Feb 2013 12:06:28 -0700, Stephen Warren <swarren@...dotorg.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.:-(
--
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/