linux-kernel - Re: [GIT PULL] Andes(nds32) Port for Linux 4.17

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]

Message-ID: <CA+55aFzwCiRrT5Ltfg0Uci7jXVRX2hw_fHp_srK_f7yacNKwwg@mail.gmail.com>
Date:   Mon, 2 Apr 2018 09:04:38 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Greentime Hu <green.hu@...il.com>
Cc:     Arnd Bergmann <arnd@...db.de>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        greentime@...estech.com
Subject: Re: [GIT PULL] Andes(nds32) Port for Linux 4.17

On Sun, Apr 1, 2018 at 11:01 PM, Greentime Hu <green.hu@...il.com> wrote:
>
> This tag contains the core nds32 Linux port(including interrupt controller
> driver and timer driver), which has been through 7 rounds of review on mailing
> list.

Can I get an overview of the nds32 architecture (uses, quirks, reasons
for existing?) to add to the initial merge message? Just an overview,
not some kind of architecture manual thing.

Yeah, yeah, I can google it myself and write something up, but it's
the kind of information I'd like to see when merging an architecture I
hadn't really ever heard about, and I suspect most others haven't
either.

                 Linus