Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Thiago Jung Bauermann via Gdb-patches <gdb-patches@sourceware.org>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH v2 2/2] gdb/testsuite: Add test for AArch64 Scalable Vector Extension
Date: Wed, 17 Aug 2022 20:46:08 +0000	[thread overview]
Message-ID: <87mtc24mzz.fsf@linaro.org> (raw)
In-Reply-To: <87o7wynyet.fsf@linaro.org>


Hello,

Thiago Jung Bauermann <thiago.bauermann@linaro.org> writes:

> Luis Machado <luis.machado@arm.com> writes:
>
>> This looks good to me overall. I'd be more comfortable with someone
>> else approving the generic bits (though they look quite obvious to
>> me).
>
> Ok, hopefully others will agree. :-)

Ping... Does any other maintainer have an opinion on the generic parts
of this patch series?

-- 
Thiago

  reply	other threads:[~2022-08-17 20:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-05  0:46 [PATCH v2 0/2] Fix bug in aarch64-linux GDB when inferior changes SVE vector length Thiago Jung Bauermann via Gdb-patches
2022-08-05  0:46 ` [PATCH v2 1/2] gdb/aarch64: Fix thread's gdbarch when SVE vector length changes Thiago Jung Bauermann via Gdb-patches
2022-08-05 17:26   ` Luis Machado via Gdb-patches
2022-08-05  0:46 ` [PATCH v2 2/2] gdb/testsuite: Add test for AArch64 Scalable Vector Extension Thiago Jung Bauermann via Gdb-patches
2022-08-05 17:23   ` Luis Machado via Gdb-patches
2022-08-05 21:57     ` Thiago Jung Bauermann via Gdb-patches
2022-08-17 20:46       ` Thiago Jung Bauermann via Gdb-patches [this message]
2022-08-18  8:56         ` Luis Machado via Gdb-patches
2022-08-18 11:37           ` Thiago Jung Bauermann via Gdb-patches
2022-08-18 13:47             ` Luis Machado via Gdb-patches
2022-08-18 14:08               ` Thiago Jung Bauermann 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=87mtc24mzz.fsf@linaro.org \
    --to=gdb-patches@sourceware.org \
    --cc=thiago.bauermann@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