Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Luis Machado via Gdb-patches <gdb-patches@sourceware.org>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org, alex.bennee@linaro.org,
	richard.henderson@linaro.org, peter.maydell@linaro.org,
	eliz@gnu.org
Subject: Re: [PATCH, v3] [gdb/aarch64] pauth: Create new feature string for pauth to prevent crashing older gdb's
Date: Fri, 14 Apr 2023 13:45:05 +0100	[thread overview]
Message-ID: <ff93da53-ae16-6c7e-153f-44c6894063b3@arm.com> (raw)
In-Reply-To: <87pm87wvjy.fsf@tromey.com>

On 4/13/23 18:17, Tom Tromey wrote:
>>>>>> "Luis" == Luis Machado <luis.machado@arm.com> writes:
> 
> Luis> Updates since v2:
> Luis> - Added NEWS entry.
> Luis> - Rewrote deprecation paragraph.
> 
> Thank you, this addresses my comment.
> 
> Tom

Thanks. I've pushed this version now.

      reply	other threads:[~2023-04-14 12:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-11 22:43 [PATCH] " Luis Machado via Gdb-patches
2023-04-12  6:05 ` Eli Zaretskii via Gdb-patches
2023-04-12  8:46   ` Luis Machado via Gdb-patches
2023-04-12  9:20     ` Eli Zaretskii via Gdb-patches
2023-04-12  9:25       ` Luis Machado via Gdb-patches
2023-04-12  9:54         ` Eli Zaretskii via Gdb-patches
2023-04-12 11:48         ` Peter Maydell via Gdb-patches
2023-04-12 11:57           ` Luis Machado via Gdb-patches
2023-04-13 13:55         ` Tom Tromey
2023-04-12 12:27 ` [PATCH, v2] " Luis Machado via Gdb-patches
2023-04-12 12:45   ` Eli Zaretskii via Gdb-patches
2023-04-13 13:56   ` Tom Tromey
2023-04-13 14:05     ` Luis Machado via Gdb-patches
2023-04-13 14:37   ` [PATCH, v3] " Luis Machado via Gdb-patches
2023-04-13 17:17     ` Tom Tromey
2023-04-14 12:45       ` Luis Machado via Gdb-patches [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=ff93da53-ae16-6c7e-153f-44c6894063b3@arm.com \
    --to=gdb-patches@sourceware.org \
    --cc=alex.bennee@linaro.org \
    --cc=eliz@gnu.org \
    --cc=luis.machado@arm.com \
    --cc=peter.maydell@linaro.org \
    --cc=richard.henderson@linaro.org \
    --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