From: Tsukasa OI <research_trasio@irq.a4lg.com>
To: Tsukasa OI <research_trasio@irq.a4lg.com>,
Nelson Chu <nelson@rivosinc.com>,
Kito Cheng <kito.cheng@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>
Cc: binutils@sourceware.org
Subject: [PATCH v2 0/1] RISC-V: Extensions from the RISC-V Profiles
Date: Mon, 30 Jan 2023 06:35:28 +0000 [thread overview]
Message-ID: <cover.1675060487.git.research_trasio@irq.a4lg.com> (raw)
In-Reply-To: <cover.1667478033.git.research_trasio@irq.a4lg.com>
Hello,
First, to whom concerned (especially, to Nelson):
I quit the job two weeks ago due to my poor health conditions and will take
some time for recuperation. Because of this (despite that I've seen all
your reviews and responses), I will not be able to respond properly (and in
a responsible manner) until... probably April or May.
Before I get busier, I will submit this one because the RISC-V Profiles
documentation is now updated (version 0.9.2, the release for TSC
recommendation to ratify) and this time, it's very unlikely to change now
(I found a typo in this but at least it's stable enough to implement).
c.f. <https://github.com/riscv/riscv-profiles/releases/tag/v0.9.2>
On PATCH v1, though the base specification (version 0.9-draft) was Frozen,
some changes are expected and I submitted it with DO NOT MERGE status.
The change actually happened and an extension name has changed ('Ssptead' ->
'Svptead' -> 'Svade'). This time, I think it's safe to upstream new
extension names.
Sincerely,
Tsukasa
Tsukasa OI (1):
RISC-V: Add platform property/capability extensions
bfd/elfxx-riscv.c | 35 ++++++++++++++++++++++++++++++++++-
1 file changed, 34 insertions(+), 1 deletion(-)
base-commit: 594a01c217143dce2f1f3181bcca4047b4a44107
--
2.39.0
next prev parent reply other threads:[~2023-01-30 6:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 12:26 [REVIEW ONLY 0/2] NEAR RATIFICATION " Tsukasa OI
2022-11-03 12:26 ` [REVIEW ONLY 1/2] NEAR-RATIFICATION RISC-V: Add 'Ssstateen' extension and its CSRs Tsukasa OI
2022-11-03 12:26 ` [REVIEW ONLY 2/2] NEAR-RATIFICATION RISC-V: Add platform property/capability extensions Tsukasa OI
2022-11-03 13:11 ` [REVIEW ONLY 0/2] NEAR RATIFICATION RISC-V: Extensions from the RISC-V Profiles Nelson Chu
2022-11-03 13:20 ` Tsukasa OI
2022-11-19 2:56 ` Tsukasa OI
2023-01-30 6:35 ` Tsukasa OI [this message]
2023-01-30 6:35 ` [PATCH v2 1/1] RISC-V: Add platform property/capability extensions Tsukasa OI
2023-01-30 7:11 ` [PATCH v3 0/1] RISC-V: Extensions from the RISC-V Profiles Tsukasa OI
2023-01-30 7:11 ` [PATCH v3 1/1] RISC-V: Add platform property/capability extensions Tsukasa OI
2023-07-26 0:05 ` [PATCH v4 0/1] RISC-V: Extensions from the RISC-V Profiles Tsukasa OI
2023-07-26 0:05 ` [PATCH v4 1/1] RISC-V: Add platform property/capability extensions Tsukasa OI
2023-07-26 0:47 ` Palmer Dabbelt
2023-07-26 1:02 ` Tsukasa OI
2023-07-31 2:56 ` Tsukasa OI
2023-01-31 4:46 ` [PATCH v2 0/1] RISC-V: Extensions from the RISC-V Profiles Nelson Chu
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=cover.1675060487.git.research_trasio@irq.a4lg.com \
--to=research_trasio@irq.a4lg.com \
--cc=binutils@sourceware.org \
--cc=kito.cheng@sifive.com \
--cc=nelson@rivosinc.com \
--cc=palmer@dabbelt.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).