From: Luis Machado <luis.machado@arm.com>
To: Yichao Yu <yyc1992@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v3] Return the regnum for PC (32) on aarch64
Date: Wed, 18 May 2022 15:03:29 +0100 [thread overview]
Message-ID: <f5ab6399-26c9-8a33-3169-76acb351e770@arm.com> (raw)
In-Reply-To: <CAMvDr+SgUcRQYRODxmkD7T5pGppzxLrDfRv_mWZptdVB0ZHUUA@mail.gmail.com>
On 5/18/22 15:01, Yichao Yu wrote:
> On Wed, May 18, 2022 at 9:36 AM Luis Machado <luis.machado@arm.com> wrote:
>>
>> On 5/18/22 14:01, Yichao Yu wrote:
>>> On Wed, May 18, 2022 at 5:54 AM Luis Machado <luis.machado@arm.com> wrote:
>>>>
>>>> On 5/18/22 02:03, Yichao Yu wrote:
>>>>> Sorry for the duplicated post.... I think somehow the university
>>>>> network prevented the email from going out earlier today...
>>>>
>>>> No problem. I've been having some inbound e-mail issues as well.
>>>
>>> I assume by this you mean that someone else will commit it. (cuz I
>>> believe I can't).
>>>
>>
>> Just to confirm, do you have a copyright assignment in place with the FSF?
>>
>> I see one of your previous patches has been pushed before by one of the maintainers.
>
> Yes I have that (*.BINUTILS.pdf{,.asc} and *.GDB.pdf{,.asc}). Assuming
> they don't expire.
>
Great. I'll push on your behalf.
Thanks for fixing this.
next prev parent reply other threads:[~2022-05-18 14:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 12:27 [PATCH] " Yichao Yu
2022-05-16 9:05 ` Luis Machado
2022-05-16 13:17 ` Yichao Yu
2022-05-16 13:25 ` [PATCH v2] " Yichao Yu
2022-05-17 6:42 ` Luis Machado
2022-05-17 14:41 ` [PATCH v3] " Yichao Yu
2022-05-17 17:34 ` [PATCH v2] " Yichao Yu
2022-05-17 17:36 ` [PATCH v3] " Yichao Yu
2022-05-18 1:03 ` Yichao Yu
2022-05-18 9:53 ` Luis Machado
2022-05-18 13:01 ` Yichao Yu
2022-05-18 13:36 ` Luis Machado
2022-05-18 14:01 ` Yichao Yu
2022-05-18 14:03 ` Luis Machado [this message]
2022-05-19 1:11 ` Yichao Yu
2022-05-16 13:29 ` [PATCH] " Luis Machado
2022-05-16 14:10 ` Yichao Yu
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=f5ab6399-26c9-8a33-3169-76acb351e770@arm.com \
--to=luis.machado@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=yyc1992@gmail.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).