From: "H.J. Lu" <hjl.tools@gmail.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: [PATCH 0/4] x86: get rid of LONG_DOUBLE_MNEM_SUFFIX and No_ldSuf
Date: Wed, 30 Nov 2022 14:25:38 -0800 [thread overview]
Message-ID: <CAMe9rOqh=2HrMQcvZzXo13C8mzgmeDkG59nt_saZPUcGumkbmw@mail.gmail.com> (raw)
In-Reply-To: <b309d824-01de-72fd-6eaf-f82475acfc02@suse.com>
On Wed, Nov 30, 2022 at 12:53 AM Jan Beulich <jbeulich@suse.com> wrote:
>
> This fake suffix has long lost its original purpose (assuming it ever
> had one fitting its name).
>
> 1: Intel: restrict use of LONG_DOUBLE_MNEM_SUFFIX
> 2: Intel: drop LONG_DOUBLE_MNEM_SUFFIX
> 3: drop No_ldSuf
> 4: rework of match_template()'s suffix checking
>
> Jan
OK to all.
Thanks.
--
H.J.
prev parent reply other threads:[~2022-11-30 22:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 8:53 Jan Beulich
2022-11-30 8:54 ` [PATCH 1/4] x86/Intel: restrict use of LONG_DOUBLE_MNEM_SUFFIX Jan Beulich
2022-11-30 8:55 ` [PATCH 2/4] x86/Intel: drop LONG_DOUBLE_MNEM_SUFFIX Jan Beulich
2022-11-30 8:55 ` [PATCH 3/4] x86: drop No_ldSuf Jan Beulich
2022-11-30 8:56 ` [PATCH 4/4] x86: rework of match_template()'s suffix checking Jan Beulich
2022-11-30 22:25 ` H.J. Lu [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='CAMe9rOqh=2HrMQcvZzXo13C8mzgmeDkG59nt_saZPUcGumkbmw@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=binutils@sourceware.org \
--cc=jbeulich@suse.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).