From: Jeff Law <jeffreyalaw@gmail.com>
To: Philipp Tomsich <philipp.tomsich@vrull.eu>
Cc: binutils@sourceware.org, Kito Cheng <kito.cheng@sifive.com>,
Nelson Chu <nelson.chu@sifive.com>,
Christoph Muellner <christoph.muellner@vrull.eu>
Subject: Re: [RFC PATCH v1] RISC-V: Support Zicond extension
Date: Tue, 20 Jun 2023 22:25:12 -0600 [thread overview]
Message-ID: <e76df367-5327-4697-2212-30a6988108c9@gmail.com> (raw)
In-Reply-To: <CAAeLtUAj=qXfi4pQ4RstAYtC8QWD-CSxd=mDki_MGD+cd803OA@mail.gmail.com>
On 6/19/23 08:21, Philipp Tomsich wrote:
> Given that the 2.41 milestone is approaching and Zicond has passed the
> FREEZE milestone (and is even out of public review already), I would
> like to move this forward.
> Is this OK for trunk? Should I resubmit with an updated commit message?
Given they were acked with "this is fine to go forward with the spec
freezes", I think they can go forward now. I think you just need to
fixup the ChangeLog a bit since it references INSN_CLASS_XVENTANACONDOPS ;-)
Jeff
next prev parent reply other threads:[~2023-06-21 4:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-21 0:29 Philipp Tomsich
2023-01-26 0:26 ` Jeff Law
2023-01-26 1:02 ` Andrew Waterman
2023-03-01 1:58 ` Nelson Chu
2023-03-01 2:03 ` Palmer Dabbelt
2023-06-19 14:21 ` Philipp Tomsich
2023-06-21 4:25 ` Jeff Law [this message]
2023-06-21 4:38 ` Palmer Dabbelt
2023-06-27 13:27 ` Jeff Law
2023-06-27 14:32 ` Philipp Tomsich
2023-06-27 23:12 ` Jeff Law
2023-06-27 23:33 ` Palmer Dabbelt
2023-06-27 14:48 ` Palmer Dabbelt
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=e76df367-5327-4697-2212-30a6988108c9@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=binutils@sourceware.org \
--cc=christoph.muellner@vrull.eu \
--cc=kito.cheng@sifive.com \
--cc=nelson.chu@sifive.com \
--cc=philipp.tomsich@vrull.eu \
/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).