From: Tom Tromey <tom@tromey.com>
To: Nelson Chu <nelson@rivosinc.com>
Cc: Tom Tromey <tom@tromey.com>,
bernd.edlinger@hotmail.de, gdb-patches@sourceware.org,
aburgess@redhat.com, vapier@gentoo.org,
binutils@sourceware.org
Subject: Re: [PATCH] sim: riscv: Fix build fail since INSN_CLASS_A was removed.
Date: Thu, 09 May 2024 08:26:48 -0600 [thread overview]
Message-ID: <87cypv2h93.fsf@tromey.com> (raw)
In-Reply-To: <CAPpQWtBh6+4JgPyZuKWcEsUbsp5ON2EFxnCKFNX9MPP1Q_Acog@mail.gmail.com> (Nelson Chu's message of "Thu, 9 May 2024 22:25:00 +0800")
>>>>> "Nelson" == Nelson Chu <nelson@rivosinc.com> writes:
Nelson> Thanks, I think it would be good to apply the fix from Bernd,
Nelson> since I'm not the expert and regular contributor of gdb ;)
Either way is fine by me. Thanks again.
Tom
next prev parent reply other threads:[~2024-05-09 14:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 0:54 Nelson Chu
2024-05-09 14:11 ` Tom Tromey
2024-05-09 14:25 ` Nelson Chu
2024-05-09 14:26 ` Tom Tromey [this message]
2024-05-09 15:06 ` Bernd Edlinger
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=87cypv2h93.fsf@tromey.com \
--to=tom@tromey.com \
--cc=aburgess@redhat.com \
--cc=bernd.edlinger@hotmail.de \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=nelson@rivosinc.com \
--cc=vapier@gentoo.org \
/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).