From: Kito Cheng <kito.cheng@gmail.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Tsukasa OI <research_trasio@irq.a4lg.com>,
Nelson Chu <nelson.chu@sifive.com>,
Kito Cheng <kito.cheng@sifive.com>,
Binutils <binutils@sourceware.org>
Subject: Re: [RESEND PATCH 1/1] RISC-V: Update Zihintpause extension version
Date: Tue, 5 Jul 2022 18:40:05 +0800 [thread overview]
Message-ID: <CA+yXCZBSBBCpv9SG_5P4sbLudH24F343uw5p=EC3aw_+OgWfFw@mail.gmail.com> (raw)
In-Reply-To: <1f0109c8-45fd-ef96-1f2a-d51dacbf2887@suse.com>
> Just for my own education: Isn't the general versioning scheme using
> 2.x only for non-draft functionality?
Version scheme has *slightly* changed, RISC-V uses 2.0 as raritfed
version number, and 2.x for non-draft functionality change,
and now RISC-V uses 1.0 as a ratified version.
More discussion you can found here:
https://sourceware.org/pipermail/binutils/2022-February/119587.html
But I must say I still can't figure out what happened on zihintpause
after reading the thread...
prev parent reply other threads:[~2022-07-05 10:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-03 10:31 [RESEND PATCH 0/1] RISC-V: Update 'Zihintpause' " Tsukasa OI
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 [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='CA+yXCZBSBBCpv9SG_5P4sbLudH24F343uw5p=EC3aw_+OgWfFw@mail.gmail.com' \
--to=kito.cheng@gmail.com \
--cc=binutils@sourceware.org \
--cc=jbeulich@suse.com \
--cc=kito.cheng@sifive.com \
--cc=nelson.chu@sifive.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).