[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y39blUaC/jHiOYCk@wendy>
Date: Thu, 24 Nov 2022 11:55:01 +0000
From: Conor Dooley <conor.dooley@...rochip.com>
To: Samuel Ortiz <sameo@...osinc.com>
CC: "Hongren (Zenithal) Zheng" <i@...ithal.me>,
Palmer Dabbelt <palmer@...osinc.com>,
Paul Walmsley <paul.walmsley@...ive.com>,
Albert Ou <aou@...s.berkeley.edu>,
Atish Patra <atishp@...osinc.com>,
Anup Patel <anup@...infault.org>,
Eric Biederman <ebiederm@...ssion.com>,
Kees Cook <keescook@...omium.org>, <linux-mm@...ck.org>,
<linux-riscv@...ts.infradead.org>, <linux-kernel@...r.kernel.org>,
<linux-api@...r.kernel.org>,
Michael Kerrisk <mtk.manpages@...il.com>,
<linux-man@...r.kernel.org>, Jiatai He <jiatai2021@...as.ac.cn>,
Heiko Stuebner <heiko@...ech.de>
Subject: Re: [PATCH v3 2/3] RISC-V: uapi: add HWCAP for Bitmanip/Scalar Crypto
On Thu, Nov 24, 2022 at 11:47:30AM +0100, Samuel Ortiz wrote:
> Patch #1 is definitely needed regardless of which interface we pick for
> exposing the ISA strings to userspace.
I took another look at #1, and I feel more confused about what
constitutes canonical order than I did before! If you know better than
I, and you probably do since you're interested in these 6 month old
patches, some insight would be appreciated!
Thanks,
Conor.
Powered by blists - more mailing lists