From: Tsukasa OI <research_trasio@irq.a4lg.com>
To: Nelson Chu <nelson.chu@sifive.com>,
Kito Cheng <kito.cheng@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Tsukasa OI <research_trasio@irq.a4lg.com>
Cc: binutils@sourceware.org
Subject: [RESEND PATCH 0/1] RISC-V: Update 'Zihintpause' extension version
Date: Sun, 3 Jul 2022 19:31:22 +0900 [thread overview]
Message-ID: <cover.1656844281.git.research_trasio@irq.a4lg.com> (raw)
Hi RISC-V folks,
`Zihintpause' extension actually has version 2.0 (not 1.0). This patch
will fix the version value.
ORIG: <https://sourceware.org/pipermail/binutils/2022-May/120978.html>
PING: <https://sourceware.org/pipermail/binutils/2022-May/120978.html>
Some discussion record:
<https://sourceware.org/pipermail/binutils/2022-February/119587.html>
Tracker on GitHub:
<https://github.com/a4lg/binutils-gdb/wiki/riscv_zihintpause_ver>
My copyright assignment is complete and I request review for
upstream merge. To me,
1. This one and
2. Zhinx fix patchset (to make it to GNU Binutils 2.39 release)
<https://sourceware.org/pipermail/binutils/2022-June/121416.html>
<https://github.com/a4lg/binutils-gdb/wiki/riscv_zhinx_quick_fix>
are two important patchsets intended for GNU Binutils 2.39 (to minimize
confusion and compatibility problems as possible).
I can say that all my other submissions can be postponed for Binutils
2.40 or later. I understand that committers are busy right now but
I think I could minimize the patchsets to review until 2.39 branch date.
I am so sorry to rush you.
Thanks,
Tsukasa
Tsukasa OI (1):
RISC-V: Update Zihintpause extension version
bfd/elfxx-riscv.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
base-commit: dcc9b683dc7d6b0c8e64bfa5e11cf0830387bb31
--
2.25.1
next reply other threads:[~2022-07-03 10:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-03 10:31 Tsukasa OI [this message]
2022-07-03 10:31 ` [RESEND PATCH 1/1] RISC-V: Update Zihintpause " Tsukasa OI
2022-07-04 1:37 ` Nelson Chu
2022-07-04 6:26 ` Jan Beulich
2022-07-05 10:40 ` Kito Cheng
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.1656844281.git.research_trasio@irq.a4lg.com \
--to=research_trasio@irq.a4lg.com \
--cc=binutils@sourceware.org \
--cc=kito.cheng@sifive.com \
--cc=nelson.chu@sifive.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).