Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S936293Ab3DIUPj (ORCPT ); Tue, 9 Apr 2013 16:15:39 -0400 Received: from mail-ob0-f178.google.com ([209.85.214.178]:37641 "EHLO mail-ob0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S936063Ab3DIUPg (ORCPT ); Tue, 9 Apr 2013 16:15:36 -0400 Message-ID: <516476E4.3050206@gmail.com> Date: Tue, 09 Apr 2013 15:15:32 -0500 From: Rob Herring User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130308 Thunderbird/17.0.4 MIME-Version: 1.0 To: Stephen Warren CC: Michal Marek , Grant Likely , linux-kbuild@vger.kernel.org, devicetree-discuss@lists.ozlabs.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [GIT PULL] dt: run C pre-processor on *.dts, create some standard headers References: <1365187610-29422-1-git-send-email-swarren@wwwdotorg.org> In-Reply-To: <1365187610-29422-1-git-send-email-swarren@wwwdotorg.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3152 Lines: 76 On 04/05/2013 01:46 PM, Stephen Warren wrote: > Rob, it might be worth keeping this in a separate branch in linux-next > so you can pull it out if it causes any issues. I've been using these > patches for quite a while now, but there's always opportunity for > surprises on architectures I don't use. I did just fix a bug when > building with O= a few days back, hence the V2 that I posted as patches. > Pulled into my for-next branch. Rob > ---------------------------------------------------------------- > > This branch enhances the support for running dtc on device tree files. > > A dedicated directory is created for header files that provide constants > for device-tree bindings. > > The kbuild dependency script processor is enhanced to support processing > the dependency outputs from multiple separate commands at once. > > The kbuild dtc rule is modified so that the C pre-processor is always > applied when compiling any device tree. > > Some standard headers are created which define common constants for GPIO, > IRQ, and ARM GIC device tree bindings. > > ---------------------------------------------------------------- > > The following changes since commit 6dbe51c251a327e012439c4772097a13df43c5b8: > > Linux 3.9-rc1 > > are available in the git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/swarren/linux-tegra.git tegra-for-3.10-dtc-cpp-chroot-std-headers > > for you to fetch changes up to 4be505d4fc7a07371a2b658469ca1dda99993ca3: > > ARM: dt: create a DT header for the GIC > > ---------------------------------------------------------------- > > Stephen Warren (7): > kbuild: create an "include chroot" for DT bindings > kbuild: fixdep: support concatenated dep files > kbuild: cmd_dtc_cpp: extract deps from both gcc -E and dtc > kbuild: always run gcc -E on *.dts, remove cmd_dtc_cpp > ARM: dt: add header to define GPIO flags > ARM: dt: add header to define IRQ flags > ARM: dt: create a DT header for the GIC > > arch/arm/boot/dts/include/dt-bindings | 1 + > include/dt-bindings/gpio/gpio.h | 15 +++ > .../dt-bindings/interrupt-controller/arm-gic.h | 22 +++++ > include/dt-bindings/interrupt-controller/irq.h | 19 ++++ > scripts/Makefile.lib | 17 ++-- > scripts/basic/fixdep.c | 93 ++++++++++++------ > 6 files changed, 125 insertions(+), 42 deletions(-) > create mode 120000 arch/arm/boot/dts/include/dt-bindings > create mode 100644 include/dt-bindings/gpio/gpio.h > create mode 100644 include/dt-bindings/interrupt-controller/arm-gic.h > create mode 100644 include/dt-bindings/interrupt-controller/irq.h > _______________________________________________ > devicetree-discuss mailing list > devicetree-discuss@lists.ozlabs.org > https://lists.ozlabs.org/listinfo/devicetree-discuss > > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/