public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Nelson Chu <nelson@rivosinc.com>
To: Tsukasa OI <research_trasio@irq.a4lg.com>
Cc: Kito Cheng <kito.cheng@sifive.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	binutils@sourceware.org
Subject: Re: [PATCH v2 0/1] RISC-V: Extensions from the RISC-V Profiles
Date: Tue, 31 Jan 2023 12:46:11 +0800	[thread overview]
Message-ID: <CAPpQWtAg4EZAdZkZL8F5H6as5gB+B_WMd22VWBr71eM90Dq2GQ@mail.gmail.com> (raw)
In-Reply-To: <cover.1675060487.git.research_trasio@irq.a4lg.com>

On Mon, Jan 30, 2023 at 2:35 PM Tsukasa OI <research_trasio@irq.a4lg.com> wrote:
>
> 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.

For me at least, I believe health and family are definitely top of
mind, so even though this news is certainly a loss for the entire
risc-v community, especially for the GNU developers and me, I still
hope that you can take this time to recover just like before.  Don't
pay too much attention to what I thought at that time, since people
always change their mind and become better with time :-)  The only
thing that won't change is everyone here wants to make upstream
better, that definitely includes you and me.  So thanks for all your
contributions and efforts before.  Take care, stay safe, looking
forward to co-work with you soon, no matter what field and what times.

Nelson

> 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.

Thanks, I will take a look at this later :)

>
> 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
>

      parent reply	other threads:[~2023-01-31  4:46 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 ` [PATCH v2 0/1] " Tsukasa OI
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   ` Nelson Chu [this message]

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=CAPpQWtAg4EZAdZkZL8F5H6as5gB+B_WMd22VWBr71eM90Dq2GQ@mail.gmail.com \
    --to=nelson@rivosinc.com \
    --cc=binutils@sourceware.org \
    --cc=kito.cheng@sifive.com \
    --cc=palmer@dabbelt.com \
    --cc=research_trasio@irq.a4lg.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).