From: Peter Maydell <peter.maydell@linaro.org>
To: Markus Armbruster <armbru@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PULL 00/15] Error reporting patches for 2021-08-26
Date: Fri, 27 Aug 2021 11:32:59 +0100 [thread overview]
Message-ID: <CAFEAcA_213jsO_45iK3a08oj7Tom+LgU_H3kgfjJMOBbtsxrZQ@mail.gmail.com> (raw)
In-Reply-To: <20210827045044.388748-1-armbru@redhat.com>
On Fri, 27 Aug 2021 at 05:50, Markus Armbruster <armbru@redhat.com> wrote:
>
> The following changes since commit c83fcfaf8a54d0d034bd0edf7bbb3b0d16669be9:
>
> Merge remote-tracking branch 'remotes/armbru/tags/pull-qapi-2021-08-26' into staging (2021-08-26 13:42:34 +0100)
>
> are available in the Git repository at:
>
> git://repo.or.cz/qemu/armbru.git tags/pull-error-2021-08-26
>
> for you to fetch changes up to f9dfae9cb6b27649085f662a863f6167650402e0:
>
> vl: Clean up -smp error handling (2021-08-26 17:15:28 +0200)
>
> ----------------------------------------------------------------
> Error reporting patches for 2021-08-26
>
Applied, thanks.
Please update the changelog at https://wiki.qemu.org/ChangeLog/6.2
for any user-visible changes.
-- PMM
prev parent reply other threads:[~2021-08-27 10:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-27 4:50 [PULL 00/15] Error reporting patches for 2021-08-26 Markus Armbruster
2021-08-27 4:50 ` [PULL 01/15] error: Use error_fatal to simplify obvious fatal errors (again) Markus Armbruster
2021-08-27 4:50 ` [PULL 02/15] spapr: Plug memory leak when we can't add a migration blocker Markus Armbruster
2021-08-27 4:50 ` [PULL 03/15] spapr: Explain purpose of ->fwnmi_migration_blocker more clearly Markus Armbruster
2021-08-27 4:50 ` [PULL 04/15] multi-process: Fix pci_proxy_dev_realize() error handling Markus Armbruster
2021-08-27 4:50 ` [PULL 05/15] vhost-scsi: Plug memory leak on migrate_add_blocker() failure Markus Armbruster
2021-08-27 4:50 ` [PULL 06/15] i386: Never free migration blocker objects instead of sometimes Markus Armbruster
2021-08-27 4:50 ` [PULL 07/15] vfio: Avoid error_propagate() after migrate_add_blocker() Markus Armbruster
2021-08-27 4:50 ` [PULL 08/15] whpx nvmm: Drop useless migrate_del_blocker() Markus Armbruster
2021-08-27 16:58 ` [EXTERNAL] " Sunil Muthuswamy
2021-08-28 9:13 ` Markus Armbruster
2021-08-27 4:50 ` [PULL 09/15] migration: Unify failure check for migrate_add_blocker() Markus Armbruster
2021-08-27 4:50 ` [PULL 10/15] migration: Handle migration_incoming_setup() errors consistently Markus Armbruster
2021-08-27 4:50 ` [PULL 11/15] microvm: Drop dead error handling in microvm_machine_state_init() Markus Armbruster
2021-08-27 4:50 ` [PULL 12/15] vhost: Clean up how VhostOpts method vhost_get_config() fails Markus Armbruster
2021-08-27 4:50 ` [PULL 13/15] vhost: Clean up how VhostOpts method vhost_backend_init() fails Markus Armbruster
2021-08-27 4:50 ` [PULL 14/15] Remove superfluous ERRP_GUARD() Markus Armbruster
2021-08-27 4:50 ` [PULL 15/15] vl: Clean up -smp error handling Markus Armbruster
2021-08-27 10:32 ` Peter Maydell [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=CAFEAcA_213jsO_45iK3a08oj7Tom+LgU_H3kgfjJMOBbtsxrZQ@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=armbru@redhat.com \
--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 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 NNTP newsgroup(s).