public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Hongtao Liu <crazylht@gmail.com>
To: Lili Cui <lili.cui@intel.com>
Cc: Binutils <binutils@sourceware.org>,
	"H.J. Lu" <hjl.tools@gmail.com>,  Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH 0/4] x86: fold a number of VEX and EVEX templates
Date: Mon, 18 Sep 2023 09:58:05 +0800	[thread overview]
Message-ID: <CAMZc-bzO+n2_GzU7twztu89uOvc=01sBu=ktSmrtCK=c-LxWsQ@mail.gmail.com> (raw)
In-Reply-To: <0690c179-ac98-d127-5ff4-b5abb725b6ae@suse.com>

On Fri, Sep 15, 2023 at 4:46 PM Jan Beulich via Binutils
<binutils@sourceware.org> wrote:
>
> The last two patches are explicitly RFC, for having a possibly unwanted
> side effect.
We're about to send out APX patches, @Lili Cui  cloud you take a look
at the series?
>
> 1: fold certain VEX and EVEX templates
> 2: fold VAES/VPCLMULQDQ VEX and EVEX templates
> 3: fold FMA VEX and EVEX templates
> 4: fold F16C VEX and EVEX templates
>
> Jan



-- 
BR,
Hongtao

  parent reply	other threads:[~2023-09-18  1:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-15  8:46 Jan Beulich
2023-09-15  8:47 ` [PATCH 1/4] x86: fold certain " Jan Beulich
2023-09-15  8:48 ` [PATCH 2/4] x86: fold VAES/VPCLMULQDQ " Jan Beulich
2023-09-15  8:48 ` [PATCH RFC 3/4] x86: fold FMA " Jan Beulich
2023-09-15  8:49 ` [PATCH RFC 4/4] x86: fold F16C " Jan Beulich
2023-09-18  1:58 ` Hongtao Liu [this message]
2023-09-18  5:47   ` [PATCH 0/4] x86: fold a number of " Cui, Lili
2023-09-18  9:38     ` Jan Beulich
2023-09-18 11:18       ` Cui, Lili
2023-09-18 11:49         ` Jan Beulich
2023-09-18 12:03           ` Cui, Lili

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='CAMZc-bzO+n2_GzU7twztu89uOvc=01sBu=ktSmrtCK=c-LxWsQ@mail.gmail.com' \
    --to=crazylht@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=hjl.tools@gmail.com \
    --cc=jbeulich@suse.com \
    --cc=lili.cui@intel.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).