From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760135Ab3BHOvt (ORCPT ); Fri, 8 Feb 2013 09:51:49 -0500 Received: from mail-we0-f175.google.com ([74.125.82.175]:54971 "EHLO mail-we0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758171Ab3BHOvs (ORCPT ); Fri, 8 Feb 2013 09:51:48 -0500 X-Greylist: delayed 377 seconds by postgrey-1.27 at vger.kernel.org; Fri, 08 Feb 2013 09:51:47 EST From: Grant Likely Subject: Re: [PATCH V8] kbuild: create a rule to run the pre-processor on *.dts files To: Stephen Warren , Michal Marek , Grant Likely , Rob Herring Cc: Srinivas KANDAGATLA , Mark Brown , Scott Wood , Sam Ravnborg , linux-kernel@vger.kernel.org, devicetree-discuss@lists.ozlabs.org, Stephen Warren In-Reply-To: <1360091188-24063-1-git-send-email-swarren@wwwdotorg.org> References: <1360091188-24063-1-git-send-email-swarren@wwwdotorg.org> Date: Fri, 08 Feb 2013 14:45:26 +0000 Message-Id: <20130208144527.0D8DD3E2C01@localhost> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 5 Feb 2013 12:06:28 -0700, Stephen Warren wrote: > From: Stephen Warren > > 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. > > Acked-by: Simon Glass > Acked-by: Jean-Christophe PLAGNIOL-VILLARD > Acked-by: Michal Marek > Acked-by: Srinivas Kandagatla > Signed-off-by: Stephen Warren 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. Once a dtsp file includes a C header, the contents of that header become part of the Device Tree ABI. If someone changes that file (ie. to renumber a series of #defines) then that will break the binding. We need a way to protect against that. Someone changing a .h file may make the assumption that it is only kernel internal and won't realize that it has external implications. I'm thinking that any dts includes need to be treated in the same way as userspace headers. We could put them into include/uapi and piggy back on the protection already afforded by that directory, or come up with something new. Any thoughts? g.