linux-kernel - Re: [PATCH v3] riscv: Using CSR numbers to access CSRs

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:   Mon, 12 Aug 2019 08:02:45 -0700
From:   Christoph Hellwig <hch@...radead.org>
To:     Bin Meng <bmeng.cn@...il.com>
Cc:     Albert Ou <aou@...s.berkeley.edu>, Anup Patel <Anup.Patel@....com>,
        Palmer Dabbelt <palmer@...ive.com>,
        Paul Walmsley <paul.walmsley@...ive.com>,
        linux-kernel@...r.kernel.org, linux-riscv@...ts.infradead.org,
        Andreas Schwab <schwab@...e.de>, Christoph Hellwig <hch@....de>
Subject: Re: [PATCH v3] riscv: Using CSR numbers to access CSRs

On Wed, Aug 07, 2019 at 09:13:38AM -0700, Bin Meng wrote:
> Since commit a3182c91ef4e ("RISC-V: Access CSRs using CSR numbers"),
> we should prefer accessing CSRs using their CSR numbers, but there
> are several leftovers like sstatus / sptbr we missed.
> 
> Signed-off-by: Bin Meng <bmeng.cn@...il.com>
> Reviewed-by: Anup Patel <anup@...infault.org>

Looks good,

Reviewed-by: Christoph Hellwig <hch@....de>