From: Nick Clifton <nickc@redhat.com>
To: Jan Beulich <jbeulich@suse.com>,
Marcus Shawcroft <marcus.shawcroft@arm.com>,
Richard Earnshaw <richard.earnshaw@arm.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: [PATCH] Arm64: re-work PR gas/27217 fix
Date: Thu, 28 Jul 2022 15:47:50 +0100 [thread overview]
Message-ID: <5ea4c999-72d8-9f16-1847-bd5434507393@redhat.com> (raw)
In-Reply-To: <d9e19bf4-928e-ec5f-1680-3fc00d3c2cd0@suse.com>
Hi Jan,
> Before the release is cut, may I ask what the plans here are? Should I
> commit this patch, are there alternative plans to address the regression,
> or is the regression intended to remain present in 2.39?
Please commit to the mainline, but leave the branch unchanged.
I am just being conservative here and letting the 2.39 release go out without
a possibly problematic change. It is my hope that by the time the 2.40 release
comes around your changes will have had enough testing on the mainline sources
that we can be confident that they do not break anything.
Cheers
Nick
prev parent reply other threads:[~2022-07-28 14:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 8:20 Jan Beulich
2022-07-28 11:37 ` Jan Beulich
2022-07-28 14:47 ` 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=5ea4c999-72d8-9f16-1847-bd5434507393@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=jbeulich@suse.com \
--cc=marcus.shawcroft@arm.com \
--cc=richard.earnshaw@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).