linux-kernel - Re: [PATCH 1/1] MIPS: Ingenic: Add CPU nodes for Ingenic 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] [day] [month] [year] [list]

Message-ID: <20200921202501.GC29322@alpha.franken.de>
Date:   Mon, 21 Sep 2020 22:25:01 +0200
From:   Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To:     周琰杰 (Zhou Yanjie) 
        <zhouyanjie@...yeetech.com>
Cc:     robh+dt@...nel.org, paul@...pouillou.net,
        linux-kernel@...r.kernel.org, linux-mips@...r.kernel.org,
        devicetree@...r.kernel.org, dongsheng.qiu@...enic.com,
        aric.pzqi@...enic.com, rick.tyliu@...enic.com,
        yanfei.li@...enic.com, sernia.zhou@...mail.com,
        zhenwenjin@...il.com
Subject: Re: [PATCH 1/1] MIPS: Ingenic: Add CPU nodes for Ingenic SoCs.

On Sat, Sep 19, 2020 at 07:38:59PM +0800, 周琰杰 (Zhou Yanjie) wrote:
> Add 'cpus' node to the jz4725b.dtsi, jz4740.dtsi, jz4770.dtsi,
> jz4780.dtsi, x1000.dtsi, and x1830.dtsi files.
> 
> Tested-by: H. Nikolaus Schaller <hns@...delico.com>
> Tested-by: Paul Boddie <paul@...die.org.uk>
> Signed-off-by: 周琰杰 (Zhou Yanjie) <zhouyanjie@...yeetech.com>
> ---
>  arch/mips/boot/dts/ingenic/jz4725b.dtsi | 14 ++++++++++++++
>  arch/mips/boot/dts/ingenic/jz4740.dtsi  | 14 ++++++++++++++
>  arch/mips/boot/dts/ingenic/jz4770.dtsi  | 15 ++++++++++++++-
>  arch/mips/boot/dts/ingenic/jz4780.dtsi  | 23 +++++++++++++++++++++++
>  arch/mips/boot/dts/ingenic/x1000.dtsi   | 14 ++++++++++++++
>  arch/mips/boot/dts/ingenic/x1830.dtsi   | 14 ++++++++++++++
>  6 files changed, 93 insertions(+), 1 deletion(-)

applied to mips-next.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]