From mboxrd@z Thu Jan 1 00:00:00 1970 From: Grant Likely Subject: Re: [PATCH V6 2/2] kbuild: run the pre-processor on *.dts files Date: Wed, 14 Nov 2012 22:25:45 +0000 Message-ID: <20121114222545.7E3943E0E2B@localhost> References: <1352753907-3316-1-git-send-email-swarren@wwwdotorg.org> <1352753907-3316-2-git-send-email-swarren@wwwdotorg.org> <20121114192548.59F093E0B7C@localhost> <50A3FC90.7030105@wwwdotorg.org> Return-path: In-Reply-To: <50A3FC90.7030105@wwwdotorg.org> Sender: linux-kernel-owner@vger.kernel.org To: Stephen Warren Cc: Michal Marek , David Gibson , Jon Loeliger , Rob Herring , Scott Wood , Mark Brown , Jean-Christophe PLAGNIOL-VILLARD , Sam Ravnborg , linux-kernel@vger.kernel.org, devicetree-discuss@lists.ozlabs.org, linux-arch@vger.kernel.org, Stephen Warren List-Id: linux-arch.vger.kernel.org On Wed, 14 Nov 2012 13:18:24 -0700, Stephen Warren wrote: > On 11/14/2012 12:25 PM, Grant Likely wrote: > > On Mon, 12 Nov 2012 13:58:27 -0700, Stephen Warren wrote: > >> From: Stephen Warren > >> > >> Modify cmd_dtc to run the C pre-processor on the input .dts file before > >> passing it to dtc for final compilation. This allows the use of #define > >> and #include within the .dts file. > > > Ugh, I'm definitely nervous about turning this on because of the long > > term implications so I'm going to punt on actually making a decision > > about it for the momemnt. However, I do have a question... > > Hmmm. So how do we get to a decision on this then? I'm punting for the evening just because I'm mentally exhausted. I'll make a decision in the next couple of days. g. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-f178.google.com ([209.85.212.178]:60397 "EHLO mail-wi0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1423505Ab2KNWZt (ORCPT ); Wed, 14 Nov 2012 17:25:49 -0500 Received: by mail-wi0-f178.google.com with SMTP id hm14so571725wib.1 for ; Wed, 14 Nov 2012 14:25:48 -0800 (PST) From: Grant Likely Subject: Re: [PATCH V6 2/2] kbuild: run the pre-processor on *.dts files In-Reply-To: <50A3FC90.7030105@wwwdotorg.org> References: <1352753907-3316-1-git-send-email-swarren@wwwdotorg.org> <1352753907-3316-2-git-send-email-swarren@wwwdotorg.org> <20121114192548.59F093E0B7C@localhost> <50A3FC90.7030105@wwwdotorg.org> Date: Wed, 14 Nov 2012 22:25:45 +0000 Message-ID: <20121114222545.7E3943E0E2B@localhost> Sender: linux-arch-owner@vger.kernel.org List-ID: To: Stephen Warren Cc: Michal Marek , David Gibson , Jon Loeliger , Rob Herring , Scott Wood , Mark Brown , Jean-Christophe PLAGNIOL-VILLARD , Sam Ravnborg , linux-kernel@vger.kernel.org, devicetree-discuss@lists.ozlabs.org, linux-arch@vger.kernel.org, Stephen Warren Message-ID: <20121114222545.DWx9ErkK92fcLOsyhnhugEmX06rGNDo5vy-uv9Ifa4k@z> On Wed, 14 Nov 2012 13:18:24 -0700, Stephen Warren wrote: > On 11/14/2012 12:25 PM, Grant Likely wrote: > > On Mon, 12 Nov 2012 13:58:27 -0700, Stephen Warren wrote: > >> From: Stephen Warren > >> > >> Modify cmd_dtc to run the C pre-processor on the input .dts file before > >> passing it to dtc for final compilation. This allows the use of #define > >> and #include within the .dts file. > > > Ugh, I'm definitely nervous about turning this on because of the long > > term implications so I'm going to punt on actually making a decision > > about it for the momemnt. However, I do have a question... > > Hmmm. So how do we get to a decision on this then? I'm punting for the evening just because I'm mentally exhausted. I'll make a decision in the next couple of days. g.