[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAB19ukFj7BiyikY7Bmnu5uWidZcBhL7Vg+Yhc8exstKj_UnRhg@mail.gmail.com>
Date: Tue, 13 Jan 2026 14:11:54 +0530
From: Sunil V L <sunilvl@....qualcomm.com>
To: Himanshu Chauhan <himanshu.chauhan@....qualcomm.com>
Cc: linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-acpi@...r.kernel.org, linux-efi@...r.kernel.org,
acpica-devel@...ts.linux.dev, paul.walmsley@...ive.com,
palmer@...belt.com, lenb@...nel.org, james.morse@....com,
tony.luck@...el.com, ardb@...nel.org, conor@...nel.org,
cleger@...osinc.com, robert.moore@...el.com,
anup.patel@....qualcomm.com
Subject: Re: [PATCH v3 07/10] riscv: Add RISC-V entries in processor type and
ISA strings
Hi Himanshu,
On Fri, Jan 9, 2026 at 2:33 PM Himanshu Chauhan
<himanshu.chauhan@....qualcomm.com> wrote:
>
> Add RISCV and RISCV32/64 strings in the in processor type and ISA strings
> respectively. These are defined for cper records.
>
I think it is better to add the reference to the ECR in the commit message.
> Signed-off-by: Himanshu Chauhan <himanshu.chauhan@....qualcomm.com>
> ---
> drivers/firmware/efi/cper.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/firmware/efi/cper.c b/drivers/firmware/efi/cper.c
> index 0232bd040f61..9d591a294327 100644
> --- a/drivers/firmware/efi/cper.c
> +++ b/drivers/firmware/efi/cper.c
> @@ -170,6 +170,7 @@ static const char * const proc_type_strs[] = {
> "IA32/X64",
> "IA64",
> "ARM",
> + "RISCV",
This should be "RISC-V" as per the ECR.
> };
>
> static const char * const proc_isa_strs[] = {
> @@ -178,6 +179,8 @@ static const char * const proc_isa_strs[] = {
> "X64",
> "ARM A32/T32",
> "ARM A64",
> + "RISCV32",
> + "RISCV64",
This should be "RV32/RV32E" and "RV64" as per the ECR approved.
Thanks,
Sunil
Powered by blists - more mailing lists