From: Luis Machado <luis.machado@arm.com>
To: Thiago Jung Bauermann <thiago.bauermann@linaro.org>,
gdb-patches@sourceware.org
Subject: Re: [PATCH v2 2/2] gdb/testsuite: Add test for AArch64 Scalable Vector Extension
Date: Thu, 18 Aug 2022 09:56:30 +0100 [thread overview]
Message-ID: <71903004-a93e-d879-6bd6-7e4c9e9c1561@arm.com> (raw)
In-Reply-To: <87mtc24mzz.fsf@linaro.org>
On 8/17/22 21:46, Thiago Jung Bauermann wrote:
>
> 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?
>
I think this can be pushed, as it is merely moving/sharing a bit of generic testsuite
code. Seems obvious enough.
Same thing for the other patch cleaning up the once-SPU-specific id field.
next prev parent reply other threads:[~2022-08-18 8:56 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
2022-08-05 0:46 ` [PATCH v2 1/2] gdb/aarch64: Fix thread's gdbarch when SVE vector length changes Thiago Jung Bauermann
2022-08-05 17:26 ` Luis Machado
2022-08-05 0:46 ` [PATCH v2 2/2] gdb/testsuite: Add test for AArch64 Scalable Vector Extension Thiago Jung Bauermann
2022-08-05 17:23 ` Luis Machado
2022-08-05 21:57 ` Thiago Jung Bauermann
2022-08-17 20:46 ` Thiago Jung Bauermann
2022-08-18 8:56 ` Luis Machado [this message]
2022-08-18 11:37 ` Thiago Jung Bauermann
2022-08-18 13:47 ` Luis Machado
2022-08-18 14:08 ` Thiago Jung Bauermann
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=71903004-a93e-d879-6bd6-7e4c9e9c1561@arm.com \
--to=luis.machado@arm.com \
--cc=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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).