Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Catalin Marinas via Gdb-patches <gdb-patches@sourceware.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: david.spickett@linaro.org,
	Luis Machado via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PING][PATCH,v5][AArch64] MTE corefile support
Date: Wed, 14 Jul 2021 14:07:03 +0100	[thread overview]
Message-ID: <20210714130702.GA9376@arm.com> (raw)
In-Reply-To: <20210711142200.GA637634@adacore.com>

On Sun, Jul 11, 2021 at 07:22:00AM -0700, Joel Brobecker wrote:
> Luis is trying to have this new feature ready for the GDB 11.1
> release. As I understand it, the AArch64-specific part has already
> been approved, so he's waiting for someone to review the rest of
> the changes. Is there a Global Maintainer who would feel comfortable
> doing so and who would have the time?

I'm a Linux kernel maintainer, so not much for me to review on the gdb
front. But feedback from the gdb maintainers would be appreciated.

W.r.t. upstreaming the feature in gdb, I'd wait until the Linux
counterpart is merged. We agreed in principle on the ABI but I wouldn't
consider it stable until the feature hits a kernel release.

-- 
Catalin

  reply	other threads:[~2021-07-14 13:07 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-18 20:20 [PATCH] [AArch64] " Luis Machado via Gdb-patches
2021-05-19 10:01 ` David Spickett via Gdb-patches
2021-05-19 11:11   ` Luis Machado via Gdb-patches
2021-05-19 12:13 ` Eli Zaretskii via Gdb-patches
2021-05-21 15:12 ` Alan Hayward via Gdb-patches
2021-05-21 15:30   ` Luis Machado via Gdb-patches
2021-05-21 17:20     ` John Baldwin
2021-05-24 13:41       ` Luis Machado via Gdb-patches
2021-05-24  8:07     ` Alan Hayward via Gdb-patches
2021-05-24 12:45       ` Luis Machado via Gdb-patches
2021-05-26 14:08 ` [PATCH,v2] " Luis Machado via Gdb-patches
2021-05-29  3:14   ` Simon Marchi via Gdb-patches
2021-05-31 14:12     ` Luis Machado via Gdb-patches
2021-05-31 14:49       ` Simon Marchi via Gdb-patches
2021-05-31 14:56         ` Luis Machado via Gdb-patches
2021-05-31 14:15   ` [PATCH,v3][AArch64] " Luis Machado via Gdb-patches
2021-05-31 16:44 ` [PATCH,v4][AArch64] " Luis Machado via Gdb-patches
2021-06-01 17:45 ` [PATCH,v5][AArch64] " Luis Machado via Gdb-patches
2021-06-15 14:10   ` [Ping][PATCH,v5][AArch64] " Luis Machado via Gdb-patches
2021-06-24 14:00   ` [PATCH,v5][AArch64] " Alan Hayward via Gdb-patches
2021-06-24 14:37     ` Luis Machado via Gdb-patches
2021-06-24 15:18       ` Alan Hayward via Gdb-patches
2021-07-01 13:50   ` [PING][PATCH,v5][AArch64] " Luis Machado via Gdb-patches
2021-07-11 14:22     ` Joel Brobecker
2021-07-14 13:07       ` Catalin Marinas via Gdb-patches [this message]
2021-07-29  2:26         ` Simon Marchi via Gdb-patches
2021-07-29 16:03           ` John Baldwin
2021-07-29 18:10           ` Catalin Marinas via Gdb-patches
2021-07-29 18:20             ` Simon Marchi via Gdb-patches
2021-08-01 15:44               ` Joel Brobecker
2021-08-02 12:06                 ` Luis Machado via Gdb-patches
2021-07-19 19:05   ` Luis Machado via Gdb-patches
2021-07-27 16:10   ` Luis Machado via Gdb-patches

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=20210714130702.GA9376@arm.com \
    --to=gdb-patches@sourceware.org \
    --cc=brobecker@adacore.com \
    --cc=catalin.marinas@arm.com \
    --cc=david.spickett@linaro.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