From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: "Alex Bennée" <alex.bennee@linaro.org>, peter.maydell@linaro.org
Cc: qemu-devel@nongnu.org
Subject: Re: [PULL 0/7] testing, gdbstub and plugin updates
Date: Tue, 25 May 2021 14:28:31 +0200 [thread overview]
Message-ID: <7ef6ac9e-27a6-451c-a511-38cd67a2bcd0@amsat.org> (raw)
In-Reply-To: <20210525112431.22005-1-alex.bennee@linaro.org>
On 5/25/21 1:24 PM, Alex Bennée wrote:
> The gprof/gcov passed on retry. I'll continue to look at it but didn't want
> to hold up the PR because of it. - Alex
>
> The following changes since commit 0dab1d36f55c3ed649bb8e4c74b9269ef3a63049:
>
> Merge remote-tracking branch 'remotes/stefanha-gitlab/tags/block-pull-request' into staging (2021-05-24 15:48:08 +0100)
>
> are available in the Git repository at:
>
> https://github.com/stsquad/qemu.git tags/pull-testing-and-misc-updates-250521-1
>
> for you to fetch changes up to bb84bcf61495e9c2907b0659a60beacd2e92e34e:
>
> plugins/syscall: Added a table-like summary output (2021-05-25 09:24:21 +0100)
>
> ----------------------------------------------------------------
> Testing, gdbstub and plugin updates
>
> - ensure gitlab references master registry
> - add special rule for hexagon image
> - clean-up gdbstub's argument handling
> - fix replay HMP commands to accept long icount
> - minor re-factor of gdbstub replay handling
> - update syscall plugin to be more useful
>
> ----------------------------------------------------------------
> Alex Bennée (5):
> gitlab: explicitly reference the upstream registry
> gitlab: add special rule for the hexagon container
FYI there is still an issue with this patch:
'build-user-hexagon' job needs 'hexagon-cross-container' job,
but it was not added to the pipeline
next prev parent reply other threads:[~2021-05-25 12:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 11:24 [PULL 0/7] testing, gdbstub and plugin updates Alex Bennée
2021-05-25 11:24 ` [PULL 1/7] gitlab: explicitly reference the upstream registry Alex Bennée
2021-05-25 11:24 ` [PULL 2/7] gitlab: add special rule for the hexagon container Alex Bennée
2021-05-25 11:24 ` [PULL 3/7] gdbstub: Constify GdbCmdParseEntry Alex Bennée
2021-05-25 11:24 ` [PULL 4/7] gdbstub: Replace GdbCmdContext with plain g_array() Alex Bennée
2021-05-25 11:24 ` [PULL 5/7] hmp-commands: expand type of icount to "l" in replay commands Alex Bennée
2021-05-25 11:24 ` [PULL 6/7] gdbstub: tidy away reverse debugging check into function Alex Bennée
2021-05-25 11:24 ` [PULL 7/7] plugins/syscall: Added a table-like summary output Alex Bennée
2021-05-25 12:28 ` Philippe Mathieu-Daudé [this message]
2021-05-25 15:05 ` [PULL 0/7] testing, gdbstub and plugin updates Alex Bennée
2021-05-25 15:15 ` Peter Maydell
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=7ef6ac9e-27a6-451c-a511-38cd67a2bcd0@amsat.org \
--to=f4bug@amsat.org \
--cc=alex.bennee@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.