mbox series

[v2,0/1] RISC-V: Extensions from the RISC-V Profiles

Message ID cover.1675060487.git.research_trasio@irq.a4lg.com
Headers
Series RISC-V: Extensions from the RISC-V Profiles |

Message

Tsukasa OI Jan. 30, 2023, 6:35 a.m. UTC 
  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

Comments

Nelson Chu Jan. 31, 2023, 4:46 a.m. UTC | #1 
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
>