From: Yang Liu <liuyang22@iscas.ac.cn>
To: Guinevere Larsen <blarsen@redhat.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Andrew Burgess <aburgess@redhat.com>,
Eli Zaretskii <eliz@gnu.org>
Cc: tom@tromey.com, gdb-patches@sourceware.org,
simon.marchi@polymtl.ca, Eli Zaretskii <eliz@gnu.org>
Subject: Re: [PATCH v3] gdb: RISC-V: Refine lr/sc sequence support
Date: Fri, 12 Jan 2024 17:07:03 +0800 [thread overview]
Message-ID: <dad6c39d-9888-404e-b509-c1d254ca497d@iscas.ac.cn> (raw)
In-Reply-To: <da01cc43-9340-466a-a0d3-fc8ddc15fb09@redhat.com>
On 2024/1/12 16:43, Guinevere Larsen wrote:
> On 12/01/2024 07:39, Palmer Dabbelt wrote:
>> 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.
>
> You got it right on what "Approved-By" means. Once Yang gets added to
> the write-after-approval list, she is free to push this commit to the
> master branch when her patch gets that tag. (Or, a maintainer can
> merge her patch in without giving that access if Yang thinks she won't
> contribute further).
I'll probably contribute more to gdb. By the way, I go by he/him
pronouns. ;)
> For the complete explanation of the tags, a patch was merged recently
> explaining how they work in the gdb/MAINTAINERS file. For convenience,
> here's a link to the final version of the text:
> https://inbox.sourceware.org/gdb-patches/20231207173415.2311804-2-blarsen@redhat.com/
>
>>
>> It looks generally reasonable to me, so
>>
>> Reviewed-by: Palmer Dabbelt <palmer@rivosinc.com>
>>
>> if that helps any...
> Hopefully this goes in soon!
Thank you all for the explanations and sorting this out!
Yang Liu
next prev parent reply other threads:[~2024-01-12 9:07 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
2024-01-12 8:43 ` Guinevere Larsen
2024-01-12 9:07 ` Yang Liu [this message]
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=dad6c39d-9888-404e-b509-c1d254ca497d@iscas.ac.cn \
--to=liuyang22@iscas.ac.cn \
--cc=aburgess@redhat.com \
--cc=blarsen@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=palmer@dabbelt.com \
--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).