linux-kernel - Re: [PATCH] ARM: at91/Documentation: add a README for Atmel SoCs

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]

Date:	Tue, 13 Jan 2015 12:26:49 +0100
From:	Nicolas Ferre <nicolas.ferre@...el.com>
To:	Olof Johansson <olof@...om.net>
CC:	<linux-arm-kernel@...ts.infradead.org>,
	<linux-kernel@...r.kernel.org>, Arnd Bergmann <arnd@...db.de>,
	<khilman@...nel.org>,
	"Jean-Christophe PLAGNIOL-VILLARD" <plagnioj@...osoft.com>,
	Boris BREZILLON <boris.brezillon@...e-electrons.com>,
	Alexandre Belloni <alexandre.belloni@...e-electrons.com>,
	Patrice Vilchez <patrice.vilchez@...el.com>,
	Ludovic Desroches <ludovic.desroches@...el.com>,
	Cyrille Pitchen <cyrille.pitchen@...el.com>,
	ARM Maintainers <arm@...nel.org>
Subject: Re: [PATCH] ARM: at91/Documentation: add a README for Atmel SoCs

Le 13/01/2015 03:03, Olof Johansson a écrit :
> On Fri, Jan 09, 2015 at 02:20:31PM +0100, Nicolas Ferre wrote:
>> Add a README file to describe Atmel SoCs (aka AT91) support in Mainline Linux:
>> - SoC list + datasheet web links
>> - Basic but useful information
>> - Device Tree conventions and Work In Progress statement.
>>
>> Signed-off-by: Nicolas Ferre <nicolas.ferre@...el.com>
>> Cc: ARM Maintainers <arm@...nel.org>
> 
> Acked-by: Olof Johansson <olof@...om.net>
> 
> With the understanding that:
> 
>> +Device Tree for AT91 SoCs and boards
>> +------------------------------------
>> +All AT91 SoCs are converted to Device Tree. Since Linux 3.19, these products
>> +must use this method to boot the Linux kernel.
>> +
>> +Work In Progress statement:
>> +Device Tree files and Device Tree bindings that apply to AT91 SoCs and boards are
>> +considered as "Unstable". To be completely clear, any at91 binding can change at
>> +any time. So, be sure to use a Device Tree Binary and a Kernel Image generated from
>> +the same source tree.
>> +Please refer to the Documentation/devicetree/bindings/ABI.txt file for a
>> +definition of a "Stable" binding/ABI.
>> +This statement will be removed by AT91 MAINTAINERS when appropriated.
> 
> While this statement is here, at the end of the day if you break a user
> you're responsible for fixing them. I.e. if a tree falls in the forest
> and nobody notices, then so be it.
> 
> But you can't break existing users and point to this and get away with
> it. However, hopefully based on this doc users will go with practices
> that means that you can revise bindings if you have to.

Yes, that was the intention.

Thanks, bye,
-- 
Nicolas Ferre
--
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/