linux-kernel - Re: [PATCH] ARM: Fix dts files w/ status property: "disable" -> "disabled"

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]

Message-ID: <4FD640B7.90106@antcom.de>
Date:	Mon, 11 Jun 2012 21:02:15 +0200
From:	Roland Stigge <stigge@...com.de>
To:	Stephen Warren <swarren@...dotorg.org>
CC:	arm@...nel.org, linux-arm-kernel@...ts.infradead.org,
	linux-kernel@...r.kernel.org, b-cousson@...com,
	grant.likely@...retlab.ca, rob.herring@...xeda.com
Subject: Re: [PATCH] ARM: Fix dts files w/ status property: "disable" -> "disabled"

On 11/06/12 19:30, Stephen Warren wrote:
> On 06/11/2012 09:11 AM, Roland Stigge wrote:
>> This patches fixes some status = "disable" strings to "disabled", the correct
>> way of disabling nodes in the devicetree.
>>
>> lpc32xx.dtsi is fixed separately in the LPC32xx patch set due to the many
>> changes there.
> 
> The Tegra parts,
> Acked-by: Stephen Warren <swarren@...dotorg.org>
> 
> Are you intending this to be applied for 3.5? If so, that's fine. If
> not, splitting it up so I can take the Tegra parts through the Tegra
> tree would reduce the possibility of conflicts.

I would only put it into v3.6. Everything works fine without it (as Arnd
described), it just confused amateurs like me. :-)

Therefore, splitting it up.

Thanks,

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