public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Luis Machado <luis.machado@arm.com>
To: Dmytro Medvied <dmytro.medvied@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] aarch64: Fix an infinite loop on bt when the core dump has an SVE section but the target does not support it.
Date: Thu, 8 Jun 2023 14:47:26 +0100	[thread overview]
Message-ID: <318300e0-6ca5-a268-f182-3e0480dad311@arm.com> (raw)
In-Reply-To: <CAJ=kipZRP1QaO-Bp=k+gGONXuAOYnqnVqypLDrVFBbBvnfOApw@mail.gmail.com>

On 6/8/23 14:28, Dmytro Medvied wrote:
> Hi Luis,
> 
> On Wed, Mar 29, 2023 at 4:07 PM Luis Machado <luis.machado@arm.com> wrote:
>>
>> Do you have a copyright assignment with the FSF so we can take your contribution? The patch
>> may be trivial, but I thought I'd check anyway.
> 
> Yes, finally I have a signed copyright assignment with the FSF. I've
> attached it to this email.
> 
> Could you guide me what I should do next?

Great! Could you please re-send the patch to this list (refreshed to the latest gdb head), also mentioning the setup you ran into
issues with (SVE hardware, then modifications to the core file etc)? Just so we can record what the issue was.

I should be able to apply your patch then.

Thanks!

      parent reply	other threads:[~2023-06-08 13:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-19 20:55 Dmytro Medvied
2023-03-27  9:42 ` Luis Machado
2023-03-29 12:42   ` Дмитро Медвєдь
2023-03-29 13:06     ` Luis Machado
     [not found]       ` <CAJ=kipZRP1QaO-Bp=k+gGONXuAOYnqnVqypLDrVFBbBvnfOApw@mail.gmail.com>
2023-06-08 13:47         ` Luis Machado [this message]

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=318300e0-6ca5-a268-f182-3e0480dad311@arm.com \
    --to=luis.machado@arm.com \
    --cc=dmytro.medvied@gmail.com \
    --cc=gdb-patches@sourceware.org \
    /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).