From: Nick Clifton <nickc@redhat.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: Arm64: assembling adrp with operand involving .
Date: Mon, 27 Jun 2022 15:34:17 +0100 [thread overview]
Message-ID: <e6bddf71-f5a2-1b16-aff2-115546ec8ace@redhat.com> (raw)
In-Reply-To: <ba71bd2a-c8e6-5b52-00f2-53a7d44ae1dd@suse.com>
Hi Jan,
> I wonder whether we can come to some sort of resolution here for 2.39.
> I'd be happy to tidy up my patch and submit it, as long as its
> downsides are understood and deemed acceptable (i.e. at least slightly
> better than the present state).
I know that you have asked me for an opinion on this problem, but the
truth is that I do not understand it well enough to have one. So I am
happy to go with whatever you feel is best. Making things better is
good, and the downsides can always be documented and if necessary,
addressed later.
Cheers
Nick
prev parent reply other threads:[~2022-06-27 14:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 7:55 Jan Beulich
2022-02-14 13:35 ` Nick Clifton
2022-02-14 14:04 ` Jan Beulich
2022-05-03 13:26 ` Jan Beulich
2022-05-09 15:21 ` Nick Clifton
2022-05-18 7:26 ` Jan Beulich
2022-06-27 14:03 ` Jan Beulich
2022-06-27 14:34 ` Nick Clifton [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=e6bddf71-f5a2-1b16-aff2-115546ec8ace@redhat.com \
--to=nickc@redhat.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).