Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yodel Eldar <yodel.eldar@gmail.com>
To: Simon Marchi <simark@simark.ca>
Cc: "Maciej W. Rozycki" <macro@orcam.me.uk>,
	gdb-patches@sourceware.org, Yodel Eldar <yodel.eldar@gmail.com>
Subject: Re: [PATCH 1/2] gdb/alpha: Add target description support
Date: Sun, 29 Jun 2025 19:08:38 -0500	[thread overview]
Message-ID: <adf74298-2e7e-421f-8326-25d32fa4ece4@gmail.com> (raw)
In-Reply-To: <24364e14-34f9-4fa5-b916-0cb8465b4d75@simark.ca>


On 6/13/25 9:34 AM, Simon Marchi wrote:
> On 6/12/25 6:07 PM, Yodel Eldar wrote:
>> On 6/12/25 3:33 PM, Simon Marchi wrote:
>>> On 2025-06-12 16:30, Simon Marchi wrote:
>>>> Thanks for the detailed investigation.  I'm not super familiar with
>>>> register descriptions and the register numbering.  I think it's better
>>>> to be on the safe side and leave it there, it shouldn't bother anybody.
>>>>
>>>>   From my non-Alpha-expert point of view, the series LGTM, so I'm tempted
>>>> to approve it.  Maciej, did you have some comments on the code?  Does it
>>>> look good to you?
>>> However, do you have a copyright assignment on file with the FSF?  This
>>> is required in order to contribute any non-trivial code.  If not, please
>>> see:
>>>
>>> https://gitweb.git.savannah.gnu.org/gitweb/?p=gnulib.git;a=blob;f=doc/Copyright/request-assign.future;hb=HEAD
>>>
>>> Simon
>>
>> Thanks for the swift response!
>>
>> I don't have an assignment on file, but I just submitted the request
>> form and await their response.
> Thanks, let us know when it's done.
>
> Simon


Happy to report that the assignment process with the FSF is now
complete!

Please let me know how to proceed.

Should I resubmit the series with the fix of the formatting error that
Eli Zaretskii noticed in the first patch?

Thanks,
Yodel


  reply	other threads:[~2025-06-30  0:09 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-26 15:12 [PATCH 0/2] gdb/alpha: Add target description support and fpcr flags Yodel Eldar
2025-05-26 15:12 ` [PATCH 1/2] gdb/alpha: Add target description support Yodel Eldar
2025-05-26 16:13   ` Eli Zaretskii
2025-05-26 17:14     ` Yodel
2025-06-03 18:49   ` Simon Marchi
2025-06-04 13:44     ` Yodel Eldar
2025-06-04 14:49       ` Maciej W. Rozycki
2025-06-04 17:29         ` Yodel Eldar
2025-06-12 19:29           ` Yodel Eldar
2025-06-12 20:30             ` Simon Marchi
2025-06-12 20:33               ` Simon Marchi
2025-06-12 22:07                 ` Yodel Eldar
2025-06-13 14:34                   ` Simon Marchi
2025-06-30  0:08                     ` Yodel Eldar [this message]
2025-07-02 17:14                       ` Simon Marchi
2025-07-02 18:51                         ` Yodel Eldar
2025-07-02 18:53               ` Maciej W. Rozycki
2025-07-02 19:02                 ` Simon Marchi
2025-07-02 19:21                   ` Maciej W. Rozycki
2025-07-02 20:52                     ` Yodel Eldar
2025-07-02 21:12                       ` Maciej W. Rozycki
2025-07-03 16:49                         ` Yodel Eldar
2025-07-03 16:02                     ` Simon Marchi
2025-07-02 18:48   ` Maciej W. Rozycki
2025-05-26 15:12 ` [PATCH 2/2] gdb/alpha: Redefine fpcr with fpcr_flags type Yodel Eldar

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=adf74298-2e7e-421f-8326-25d32fa4ece4@gmail.com \
    --to=yodel.eldar@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=macro@orcam.me.uk \
    --cc=simark@simark.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