From: Heiko Stuebner <heiko.stuebner@vrull.eu>
To: Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
linux-riscv@lists.infradead.org
Cc: "Samuel Ortiz" <sameo@rivosinc.com>,
linux@rivosinc.com, "Conor Dooley" <conor.dooley@microchip.com>,
"Andrew Jones" <ajones@ventanamicro.com>,
"Anup Patel" <apatel@ventanamicro.com>,
linux-kernel@vger.kernel.org,
"Hongren (Zenithal) Zheng" <i@zenithal.me>,
"Guo Ren" <guoren@kernel.org>,
"Atish Patra" <atishp@rivosinc.com>,
"Björn Töpel" <bjorn@rivosinc.com>,
"Evan Green" <evan@rivosinc.com>,
"Samuel Ortiz" <sameo@rivosinc.com>
Subject: Re: [PATCH v2 2/3] RISC-V: hwprobe: Expose Zbc and the scalar crypto extensions
Date: Sun, 09 Jul 2023 13:31:51 +0200 [thread overview]
Message-ID: <3506917.iIbC2pHGDl@phil> (raw)
In-Reply-To: <20230628131442.3022772-3-sameo@rivosinc.com>
Am Mittwoch, 28. Juni 2023, 15:14:34 CEST schrieb Samuel Ortiz:
> Zbc was missing from a previous Bit-Manipulation extension hwprobe
> patch.
>
> Add all scalar crypto extensions bits, and define a macro for setting
> the hwprobe key/pair in a more readable way.
>
> Reviewed-by: Evan Green <evan@rivosinc.com>
> Signed-off-by: Samuel Ortiz <sameo@rivosinc.com>
Reviewed-by: Heiko Stuebner <heiko.stuebner@vrull.eu>
Tested-by: Heiko Stuebner <heiko.stuebner@vrull.eu>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Heiko Stuebner <heiko.stuebner@vrull.eu>
To: Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
linux-riscv@lists.infradead.org
Cc: "Samuel Ortiz" <sameo@rivosinc.com>,
linux@rivosinc.com, "Conor Dooley" <conor.dooley@microchip.com>,
"Andrew Jones" <ajones@ventanamicro.com>,
"Anup Patel" <apatel@ventanamicro.com>,
linux-kernel@vger.kernel.org,
"Hongren (Zenithal) Zheng" <i@zenithal.me>,
"Guo Ren" <guoren@kernel.org>,
"Atish Patra" <atishp@rivosinc.com>,
"Björn Töpel" <bjorn@rivosinc.com>,
"Evan Green" <evan@rivosinc.com>,
"Samuel Ortiz" <sameo@rivosinc.com>
Subject: Re: [PATCH v2 2/3] RISC-V: hwprobe: Expose Zbc and the scalar crypto extensions
Date: Sun, 09 Jul 2023 13:31:51 +0200 [thread overview]
Message-ID: <3506917.iIbC2pHGDl@phil> (raw)
In-Reply-To: <20230628131442.3022772-3-sameo@rivosinc.com>
Am Mittwoch, 28. Juni 2023, 15:14:34 CEST schrieb Samuel Ortiz:
> Zbc was missing from a previous Bit-Manipulation extension hwprobe
> patch.
>
> Add all scalar crypto extensions bits, and define a macro for setting
> the hwprobe key/pair in a more readable way.
>
> Reviewed-by: Evan Green <evan@rivosinc.com>
> Signed-off-by: Samuel Ortiz <sameo@rivosinc.com>
Reviewed-by: Heiko Stuebner <heiko.stuebner@vrull.eu>
Tested-by: Heiko Stuebner <heiko.stuebner@vrull.eu>
next prev parent reply other threads:[~2023-07-09 11:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 13:14 [PATCH v2 0/3] RISC-V: archrandom support Samuel Ortiz
2023-06-28 13:14 ` Samuel Ortiz
2023-06-28 13:14 ` [PATCH v2 1/3] RISC-V: add Bitmanip/Scalar Crypto parsing from DT Samuel Ortiz
2023-06-28 13:14 ` Samuel Ortiz
2023-06-28 17:22 ` Evan Green
2023-06-28 17:22 ` Evan Green
2023-07-06 13:40 ` Conor Dooley
2023-07-06 13:40 ` Conor Dooley
2023-07-09 11:30 ` Heiko Stuebner
2023-07-09 11:30 ` Heiko Stuebner
2023-06-28 13:14 ` [PATCH v2 2/3] RISC-V: hwprobe: Expose Zbc and the scalar crypto extensions Samuel Ortiz
2023-06-28 13:14 ` Samuel Ortiz
2023-07-06 13:32 ` Conor Dooley
2023-07-06 13:32 ` Conor Dooley
2023-07-09 11:31 ` Heiko Stuebner [this message]
2023-07-09 11:31 ` Heiko Stuebner
2023-06-28 13:14 ` [PATCH v2 3/3] RISC-V: Implement archrandom when Zkr is available Samuel Ortiz
2023-06-28 13:14 ` Samuel Ortiz
2023-07-06 13:33 ` Conor Dooley
2023-07-06 13:33 ` Conor Dooley
2023-07-13 0:21 ` Guo Ren
2023-07-13 0:21 ` Guo Ren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3506917.iIbC2pHGDl@phil \
--to=heiko.stuebner@vrull.eu \
--cc=ajones@ventanamicro.com \
--cc=aou@eecs.berkeley.edu \
--cc=apatel@ventanamicro.com \
--cc=atishp@rivosinc.com \
--cc=bjorn@rivosinc.com \
--cc=conor.dooley@microchip.com \
--cc=evan@rivosinc.com \
--cc=guoren@kernel.org \
--cc=i@zenithal.me \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux@rivosinc.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=sameo@rivosinc.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.