From: Jan Beulich <jbeulich@suse.com>
To: Richard Earnshaw <rearnsha@arm.com>,
Marcus Shawcroft <marcus.shawcroft@arm.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: Ping: [PATCH 0/2] Arm64/gas: adjustments to features' prereqs
Date: Fri, 10 Mar 2023 10:58:55 +0100 [thread overview]
Message-ID: <81ee6ee2-668f-2817-a8ed-b2211ca7253d@suse.com> (raw)
In-Reply-To: <e2c19d05-6ac7-6a02-6983-f3679d6aa6e5@suse.com>
On 24.02.2023 13:55, Jan Beulich via Binutils wrote:
> On 13.02.2023 09:11, Jan Beulich via Binutils wrote:
>> There are both missing and redundant ones, the former being a bug
>> while the latter being merely inconsistent.
>>
>> 1: add missing prereq features
>> 2: drop redundant feature prereqs
>
> Aarch64 maintainers - any opinion?
In the absence of feedback I guess I'm going to commit these then.
Apologies in advance in case I've overlooked anything.
Jan
prev parent reply other threads:[~2023-03-10 9:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 8:11 Jan Beulich
2023-02-13 8:12 ` [PATCH 1/2] Arm64/gas: add missing prereq features Jan Beulich
2023-02-13 8:12 ` [PATCH 2/2] Arm64/gas: drop redundant feature prereqs Jan Beulich
2023-02-24 12:55 ` Ping: [PATCH 0/2] Arm64/gas: adjustments to features' prereqs Jan Beulich
2023-03-10 9:58 ` Jan Beulich [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=81ee6ee2-668f-2817-a8ed-b2211ca7253d@suse.com \
--to=jbeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=marcus.shawcroft@arm.com \
--cc=rearnsha@arm.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).