linux-kernel - Re: [PATCH 0/2] ARM dts: bcm281xx: use preprocessor for device trees

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20130611070344.GF6688@quad.lixom.net>
Date:	Tue, 11 Jun 2013 00:03:44 -0700
From:	Olof Johansson <olof@...om.net>
To:	Matt Porter <matt.porter@...aro.org>
Cc:	Christian Daudt <csd@...adcom.com>, Arnd Bergmann <arnd@...db.de>,
	Stephen Warren <swarren@...dia.com>,
	Linux ARM Kernel List <linux-arm-kernel@...ts.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linaro Patches <patches@...aro.org>
Subject: Re: [PATCH 0/2] ARM dts: bcm281xx: use preprocessor for device trees

On Thu, Jun 06, 2013 at 01:41:33AM -0400, Matt Porter wrote:
> This series follows the same approach as taken on Tegra and
> OMAP DT files to use the C preprocessor in order to improve
> readability. Since bcm281xx does not yet have gpio and pinctrl
> support, this series just enables the C preprocessor and removes
> the magic constants from existing irq properties. Any new
> additions can come in using human readable definitions.
> 
> The resulting dtb was diff-tested to validate it versus the non
> preprocessed dts version.
> 
> Matt Porter (2):
>   ARM: dts: bcm281xx: use #include for device tree files
>   ARM: dts: bcm281xx: use existing defines for irqs

Acked-by: Olof Johansson <olof@...om.net>

Not sure what else you'll have for 3.11 devicetree-wise, Christian -- your
choice if you want to send a pull request or ack these and we'll apply them
directly.


-Olof
--
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/