From: Tom Tromey <tom@tromey.com>
To: Andrew Burgess <aburgess@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/3] Improvements to make-check-all.sh and check-all-boards
Date: Tue, 21 Jul 2026 10:48:33 -0600 [thread overview]
Message-ID: <878q74waou.fsf@tromey.com> (raw)
In-Reply-To: <cover.1784373976.git.aburgess@redhat.com> (Andrew Burgess's message of "Sat, 18 Jul 2026 12:27:24 +0100")
>>>>> "Andrew" == Andrew Burgess <aburgess@redhat.com> writes:
Andrew> Some minor improvements to the 'make check-all-boards' rule and the
Andrew> underlying make-check-all.sh script.
These all seem fine to me, thank you.
Approved-By: Tom Tromey <tom@tromey.com>
Tom
next prev parent reply other threads:[~2026-07-21 16:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-18 11:27 Andrew Burgess
2026-07-18 11:27 ` [PATCH 1/3] gdb/testsuite: missing ';' in check-all-boards rule Andrew Burgess
2026-07-18 11:27 ` [PATCH 2/3] gdb/testsuite: fix shellcheck issues in make-check-all.sh Andrew Burgess
2026-07-18 11:27 ` [PATCH 3/3] gdb/testsuite: improve rerun scripts generated by make-check-all.sh Andrew Burgess
2026-07-21 16:48 ` Tom Tromey [this message]
2026-07-23 16:42 ` [PATCH 0/3] Improvements to make-check-all.sh and check-all-boards Andrew Burgess
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=878q74waou.fsf@tromey.com \
--to=tom@tromey.com \
--cc=aburgess@redhat.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