From: Palmer Dabbelt <palmer@dabbelt.com>
To: liuyang22@iscas.ac.cn, Andrew Burgess <aburgess@redhat.com>
Cc: tom@tromey.com, gdb-patches@sourceware.org, simon.marchi@polymtl.ca
Subject: Re: [PATCH v3] gdb: RISC-V: Refine lr/sc sequence support
Date: Thu, 11 Jan 2024 22:39:08 -0800 (PST) [thread overview]
Message-ID: <mhng-85403900-88ec-4d4b-b2f0-33b541de21ed@palmer-ri-x1c9> (raw)
In-Reply-To: <edf2f2f6-2e86-4c26-a1a1-88d7d1ed122e@iscas.ac.cn>
On Thu, 11 Jan 2024 22:27:32 PST (-0800), liuyang22@iscas.ac.cn wrote:
> On 2024/1/12 02:09, Tom Tromey wrote:
>
>>>>>>> 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.
>
> I'm an employee of ISCAS (Institute of Software Chinese Academy of
> Sciences), we've signed the copyright papers to binutils-gdb. Please
> help arrange this.
As far as I can tell the ISCAS copyright assignment includes GDB. Maybe
Andrew just reviewed it thinking you guys had commit access? I'm not
exactly sure what "Approved-By" means.
It looks generally reasonable to me, so
Reviewed-by: Palmer Dabbelt <palmer@rivosinc.com>
if that helps any...
>
> Thanks,
>
> Yang Liu
next prev parent reply other threads:[~2024-01-12 6:39 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
2024-01-12 6:27 ` Yang Liu
2024-01-12 6:39 ` Palmer Dabbelt [this message]
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=mhng-85403900-88ec-4d4b-b2f0-33b541de21ed@palmer-ri-x1c9 \
--to=palmer@dabbelt.com \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=liuyang22@iscas.ac.cn \
--cc=simon.marchi@polymtl.ca \
--cc=tom@tromey.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).