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  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:   Mon, 23 Jan 2017 19:36:08 +0100
From:   Andreas Färber <afaerber@...e.de>
To:     Rob Herring <robh@...nel.org>
Cc:     linux-amlogic@...ts.infradead.org, Carlo Caione <carlo@...one.org>,
        Kevin Hilman <khilman@...libre.com>,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
        Mark Rutland <mark.rutland@....com>, devicetree@...r.kernel.org
Subject: Re: [PATCH 01/18] Documentation: devicetree: amlogic: Reorder boards

Am 23.01.2017 um 17:48 schrieb Rob Herring:
> On Fri, Jan 20, 2017 at 11:21:01PM +0100, Andreas Färber wrote:
>> Enforce groupment by SoCs and order alphabetically within the group
>> (with some exceptions). This should facilitate adding new boards.
>>
>> Signed-off-by: Andreas Färber <afaerber@...e.de>
>> ---
>>  Documentation/devicetree/bindings/arm/amlogic.txt | 19 +++++++++++++------
>>  1 file changed, 13 insertions(+), 6 deletions(-)
>>
>> diff --git a/Documentation/devicetree/bindings/arm/amlogic.txt b/Documentation/devicetree/bindings/arm/amlogic.txt
>> index c246cd2730d9..b03d23c9ea78 100644
>> --- a/Documentation/devicetree/bindings/arm/amlogic.txt
>> +++ b/Documentation/devicetree/bindings/arm/amlogic.txt
>> @@ -29,23 +29,30 @@ Boards with the Amlogic Meson GXM S912 SoC shall have the following properties:
>>    Required root node property:
>>      compatible: "amlogic,s912", "amlogic,meson-gxm";
>>  
>> -Board compatible values:
>> +Board compatible values (grouped by SoC):
> 
> ...and alphabetical order within each SoC.

...except for pro, meta, telos, which are in increasing feature set
order - should we reorder them, or ignore but still write alphabetical?

Regards,
Andreas

> 
>> +
>>    - "geniatech,atv1200" (Meson6)
>> +
>>    - "minix,neo-x8" (Meson8)
>> -  - "tronfy,mxq" (Meson8b)
>> +
>>    - "hardkernel,odroid-c1" (Meson8b)
>> +  - "tronfy,mxq" (Meson8b)
>> +
>> +  - "amlogic,p200" (Meson gxbb)
>> +  - "amlogic,p201" (Meson gxbb)
>> +  - "hardkernel,odroid-c2" (Meson gxbb)
>> +  - "nexbox,a95x" (Meson gxbb or Meson gxl s905x)
>>    - "tronsmart,vega-s95-pro", "tronsmart,vega-s95" (Meson gxbb)
>>    - "tronsmart,vega-s95-meta", "tronsmart,vega-s95" (Meson gxbb)
>>    - "tronsmart,vega-s95-telos", "tronsmart,vega-s95" (Meson gxbb)
>> -  - "hardkernel,odroid-c2" (Meson gxbb)
>> -  - "amlogic,p200" (Meson gxbb)
>> -  - "amlogic,p201" (Meson gxbb)
>>    - "wetek,hub" (Meson gxbb)
>>    - "wetek,play2" (Meson gxbb)
>> +
>>    - "amlogic,p212" (Meson gxl s905x)
>> +
>>    - "amlogic,p230" (Meson gxl s905d)
>>    - "amlogic,p231" (Meson gxl s905d)
>> +
>>    - "amlogic,q200" (Meson gxm s912)
>>    - "amlogic,q201" (Meson gxm s912)
>> -  - "nexbox,a95x" (Meson gxbb or Meson gxl s905x)
>>    - "nexbox,a1" (Meson gxm s912)
>> -- 
>> 2.10.2
>>


-- 
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)

Powered by blists - more mailing lists