Linux-RISC-V Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Walmsley <pjw@kernel.org>
To: Guodong Xu <guodong@riscstar.com>
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	 Conor Dooley <conor+dt@kernel.org>,
	 Samuel Holland <samuel.holland@sifive.com>,
	 Heinrich Schuchardt <heinrich.schuchardt@canonical.com>,
	 Paul Walmsley <pjw@kernel.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	 Albert Ou <aou@eecs.berkeley.edu>,
	Alexandre Ghiti <alex@ghiti.fr>,  Evan Green <evan@rivosinc.com>,
	Andrew Jones <ajones@ventanamicro.com>,
	 Conor Dooley <conor.dooley@microchip.com>,
	 Paul Walmsley <paul.walmsley@sifive.com>,
	Conor Dooley <conor@kernel.org>,
	 devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
	 linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] riscv: cpufeature: Clarify ISA spec version for canonical order
Date: Thu, 6 Aug 2026 12:11:07 -0600 (MDT)	[thread overview]
Message-ID: <fa0c32d5-292a-d502-bdda-dd876192d1cc@kernel.org> (raw)
In-Reply-To: <20260125-supm-ext-id-v2-3-1e3b9714c860@riscstar.com>

On Sun, 25 Jan 2026, Guodong Xu wrote:

> Specify that chapter 27 refers to version 20191213 of the RISC-V ISA
> Unprivileged Architecture. The chapter numbering differs across
> specification versions - for example, in version 20250508, the ISA
> Extension Naming Conventions is chapter 36, not chapter 27.
> 
> Historical versions of the RISC-V specification can be found via Link [1].
> 
> Acked-by: Conor Dooley <conor.dooley@microchip.com>
> Link: https://riscv.org/specifications/ratified/ [1]
> Fixes: 99e2266f2460 ("RISC-V: clarify ISA string ordering rules in cpu.c")
> Signed-off-by: Guodong Xu <guodong@riscstar.com>

Thanks, queued for v7.3.


- Paul

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2026-08-06 18:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-25  1:36 [PATCH v2 0/3] riscv: cpufeature: Add Supm extension id and validation Guodong Xu
2026-01-25  1:36 ` [PATCH v2 1/3] dt-bindings: riscv: Add Supm extension description Guodong Xu
2026-01-28 20:10   ` Conor Dooley
2026-01-25  1:36 ` [PATCH v2 2/3] riscv: cpufeature: Add ISA extension parsing for Supm Guodong Xu
2026-03-08 18:20   ` Samuel Holland
2026-01-25  1:36 ` [PATCH v2 3/3] riscv: cpufeature: Clarify ISA spec version for canonical order Guodong Xu
2026-08-06 18:11   ` Paul Walmsley [this message]
2026-03-06 18:05 ` (subset) [PATCH v2 0/3] riscv: cpufeature: Add Supm extension id and validation Conor Dooley
2026-04-30  3:25 ` patchwork-bot+linux-riscv

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=fa0c32d5-292a-d502-bdda-dd876192d1cc@kernel.org \
    --to=pjw@kernel.org \
    --cc=ajones@ventanamicro.com \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=conor+dt@kernel.org \
    --cc=conor.dooley@microchip.com \
    --cc=conor@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=evan@rivosinc.com \
    --cc=guodong@riscstar.com \
    --cc=heinrich.schuchardt@canonical.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=robh@kernel.org \
    --cc=samuel.holland@sifive.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox