linux-kernel - Re: [PATCH v1 2/7] dt-bindings: iio: rockchip-saradc: add support for rk3328

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:   Sun, 19 Mar 2017 10:34:22 +0000
From:   Jonathan Cameron <jic23@...nel.org>
To:     Heiko Stuebner <heiko@...ech.de>, cl@...k-chips.com
Cc:     robh+dt@...nel.org, mark.rutland@....com, zhengxing@...k-chips.com,
        andy.yan@...k-chips.com, jay.xu@...k-chips.com,
        matthias.bgg@...il.com, paweljarosz3691@...il.com,
        devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
        linux-rockchip@...ts.infradead.org, linux-kernel@...r.kernel.org,
        wsa@...-dreams.de, linux-i2c@...r.kernel.org, knaack.h@....de,
        lars@...afoo.de, pmeerw@...erw.net, wxt@...k-chips.com,
        david.wu@...k-chips.com, linux-iio@...r.kernel.org,
        shawn.lin@...k-chips.com, akpm@...ux-foundation.org,
        dianders@...omium.org, yamada.masahiro@...ionext.com,
        catalin.marinas@....com, will.deacon@....com, afaerber@...e.de,
        shawnguo@...nel.org, khilman@...libre.com, arnd@...db.de,
        fabio.estevam@....com, zhangqing@...k-chips.com,
        kever.yang@...k-chips.com, tony.xie@...k-chips.com,
        huangtao@...k-chips.com, yhx@...k-chips.com,
        rocky.hao@...k-chips.com
Subject: Re: [PATCH v1 2/7] dt-bindings: iio: rockchip-saradc: add support for
 rk3328

On 16/03/17 08:28, Heiko Stuebner wrote:
> Am Mittwoch, 15. März 2017, 18:03:52 CET schrieb cl@...k-chips.com:
>> From: Chen Liang <cl@...k-chips.com>
>>
>> The rk3328 saradc is the same as rk3399.
>>
>> Signed-off-by: Chen Liang <cl@...k-chips.com>
>> ---
>>  Documentation/devicetree/bindings/iio/adc/rockchip-saradc.txt | 1 +
>>  1 file changed, 1 insertion(+)
>>
>> diff --git a/Documentation/devicetree/bindings/iio/adc/rockchip-saradc.txt
>> b/Documentation/devicetree/bindings/iio/adc/rockchip-saradc.txt index
>> 205593f..f81bc20 100644
>> --- a/Documentation/devicetree/bindings/iio/adc/rockchip-saradc.txt
>> +++ b/Documentation/devicetree/bindings/iio/adc/rockchip-saradc.txt
>> @@ -5,6 +5,7 @@ Required properties:
>>     - "rockchip,saradc": for rk3188, rk3288
>>     - "rockchip,rk3066-tsadc": for rk3036
>>     - "rockchip,rk3399-saradc": for rk3399
>> +   - "rockchip,rk3328-saradc", "rockchip,rk3399-saradc": for rk3328
> 
> not sure how iio people see that, but I would suggest keeping the order, so 
> put rk3328 above rk3399.
In my case I'm not that fussed either way. Still if this list keeps growing
I can see it would be better to keep it in numeric order!

Jonathan
> 
> Heiko
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>