From: Paul Walmsley <pjw@kernel.org>
To: Guodong Xu <guodong@riscstar.com>
Cc: Jonathan Corbet <corbet@lwn.net>, Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
Conor Dooley <conor.dooley@microchip.com>,
Conor Dooley <conor@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Chen Wang <unicorn_wang@outlook.com>,
Inochi Amaoto <inochiama@gmail.com>, Yixun Lan <dlan@gentoo.org>,
Conor Dooley <conor+dt@kernel.org>,
Junhui Liu <junhui.liu@pigmoral.tech>,
linux-doc@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
sophgo@lists.linux.dev, spacemit@lists.linux.dev
Subject: Re: [PATCH v2 1/4] Documentation: riscv: uabi: Clarify ISA spec version for canonical order
Date: Wed, 14 Jan 2026 17:10:16 -0700 (MST) [thread overview]
Message-ID: <e91054c8-d7fc-5b0f-2821-9926561f64d5@kernel.org> (raw)
In-Reply-To: <20260115-adding-b-dtsi-v2-1-254dd61cf947@riscstar.com>
On Thu, 15 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: Paul Walmsley <pjw@kernel.org>
> Link: https://riscv.org/specifications/ratified/ [1]
> Fixes: f07b2b3f9d47 ("Documentation: riscv: add a section about ISA string ordering in /proc/cpuinfo")
> Signed-off-by: Guodong Xu <guodong@riscstar.com>
Thanks, queued for v6.19-rc fixes.
- Paul
next prev parent reply other threads:[~2026-01-15 0:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-14 23:18 [PATCH v2 0/4] riscv: dts: Add "b" ISA extension to existing devicetrees Guodong Xu
2026-01-14 23:18 ` [PATCH v2 1/4] Documentation: riscv: uabi: Clarify ISA spec version for canonical order Guodong Xu
2026-01-15 0:10 ` Paul Walmsley [this message]
2026-01-14 23:18 ` [PATCH v2 2/4] riscv: dts: anlogic: dr1v90: Add "b" ISA extension Guodong Xu
2026-01-15 2:25 ` Junhui Liu
2026-01-14 23:18 ` [PATCH v2 3/4] riscv: dts: sophgo: sg2044: " Guodong Xu
2026-01-15 0:28 ` Inochi Amaoto
2026-01-14 23:19 ` [PATCH v2 4/4] riscv: dts: spacemit: k1: " Guodong Xu
2026-01-15 0:39 ` Yixun Lan
2026-01-15 11:24 ` (subset) [PATCH v2 0/4] riscv: dts: Add "b" ISA extension to existing devicetrees Yixun Lan
2026-01-15 19:13 ` Conor Dooley
2026-01-15 23:04 ` Guodong Xu
2026-01-20 1:16 ` (subset) " Inochi Amaoto
2026-01-20 2:48 ` Inochi Amaoto
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=e91054c8-d7fc-5b0f-2821-9926561f64d5@kernel.org \
--to=pjw@kernel.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=dlan@gentoo.org \
--cc=guodong@riscstar.com \
--cc=inochiama@gmail.com \
--cc=junhui.liu@pigmoral.tech \
--cc=krzk+dt@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=robh@kernel.org \
--cc=sophgo@lists.linux.dev \
--cc=spacemit@lists.linux.dev \
--cc=unicorn_wang@outlook.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