From: Palmer Dabbelt <palmer@dabbelt.com>
To: Nick Clifton <nickc@redhat.com>
Cc: jbeulich@suse.com, Andrew Waterman <andrew@sifive.com>,
Jim Wilson <jim.wilson.gcc@gmail.com>,
nelson@rivosinc.com, binutils@sourceware.org
Subject: Re: [PATCH] gas/RISC-V: adjust assembler for opcode table re-ordering
Date: Tue, 10 Jan 2023 12:14:22 -0800 (PST) [thread overview]
Message-ID: <mhng-20c752d8-5466-4e6e-8a69-427e6e27fd73@palmer-ri-x1c9a> (raw)
In-Reply-To: <8a1ce779-de70-f4f1-5cdb-e828a8677e6a@redhat.com>
On Tue, 10 Jan 2023 04:31:01 PST (-0800), Nick Clifton wrote:
> Hi Jan,
>
>>>> PR gas/29940
>
>> With 2.40 scheduled to be cut in less than a week, may I ask for an arch
>> maintainer's view here?
>>
>> Nick, to save a round trip, could you confirm (or otherwise) that this
>> fix is then also fine to go on the branch (after having gone into master)?
>
> If the arch maintainer approves, then yes, backporting this patch to the 2.40
> branch is also approved.
Reviewed-by: Palmer Dabbelt <palmer@rivosinc.com>
I'm still hitting some glibc/multili issues, but this doesn't appear to
make anything worse so IMO we're better off just taking this now. I'll
try and sort out what's up on my end.
Thanks!
prev parent reply other threads:[~2023-01-10 20:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 12:34 Jan Beulich
2023-01-07 23:29 ` Aurelien Jarno
2023-01-09 17:07 ` Jan Beulich
2023-01-09 19:07 ` Palmer Dabbelt
2023-01-09 21:59 ` Maciej W. Rozycki
2023-01-10 9:25 ` Jan Beulich
2023-01-10 22:58 ` Maciej W. Rozycki
2023-01-11 9:28 ` Jan Beulich
2023-01-12 1:28 ` Maciej W. Rozycki
2023-01-12 8:26 ` Jan Beulich
2023-01-12 8:40 ` Andrew Waterman
2023-01-10 12:31 ` Nick Clifton
2023-01-10 20:14 ` Palmer Dabbelt [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=mhng-20c752d8-5466-4e6e-8a69-427e6e27fd73@palmer-ri-x1c9a \
--to=palmer@dabbelt.com \
--cc=andrew@sifive.com \
--cc=binutils@sourceware.org \
--cc=jbeulich@suse.com \
--cc=jim.wilson.gcc@gmail.com \
--cc=nelson@rivosinc.com \
--cc=nickc@redhat.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).