From: Tom Tromey <tom@tromey.com>
To: Yang Liu <liuyang22@iscas.ac.cn>
Cc: Andrew Burgess <aburgess@redhat.com>,
gdb-patches@sourceware.org, palmer@dabbelt.com,
simon.marchi@polymtl.ca
Subject: Re: [PATCH v3] gdb: RISC-V: Refine lr/sc sequence support
Date: Thu, 11 Jan 2024 11:09:05 -0700 [thread overview]
Message-ID: <87r0inpwse.fsf@tromey.com> (raw)
In-Reply-To: <47a9f437-0aee-43b7-abb7-89782f4c1b9b@iscas.ac.cn> (Yang Liu's message of "Mon, 8 Jan 2024 19:37:45 +0800")
>>>>> Yang Liu <liuyang22@iscas.ac.cn> writes:
> A gentle reminder: this patch has been approved for some time now, but
> I've noticed it hasn't been merged into the codebase. Has it been
> overlooked?
I don't really know the status of this, but if you have copyright papers
in place, we can arrange for write-after-approval access.
If you don't then I suspect we will need them, because this patch is
over the size limit.
Tom
next prev parent reply other threads:[~2024-01-11 18:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 6:58 Yang Liu
2023-11-08 11:15 ` Andrew Burgess
2024-01-08 11:37 ` Yang Liu
2024-01-11 18:09 ` Tom Tromey [this message]
2024-01-12 6:27 ` Yang Liu
2024-01-12 6:39 ` Palmer Dabbelt
2024-01-12 8:43 ` Guinevere Larsen
2024-01-12 9:07 ` Yang Liu
2024-01-12 8:44 ` Eli Zaretskii
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=87r0inpwse.fsf@tromey.com \
--to=tom@tromey.com \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=liuyang22@iscas.ac.cn \
--cc=palmer@dabbelt.com \
--cc=simon.marchi@polymtl.ca \
/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