From: Richard Henderson <richard.henderson@linaro.org>
To: Fabiano Rosas <farosas@suse.de>, qemu-devel@nongnu.org
Cc: Peter Xu <peterx@redhat.com>
Subject: Re: [PULL v2 00/13] Migration patches for 2024-05-08
Date: Fri, 10 May 2024 07:38:51 +0200 [thread overview]
Message-ID: <0e971b27-102f-423d-9db2-95810a921ae3@linaro.org> (raw)
In-Reply-To: <20240508233541.2403-1-farosas@suse.de>
On 5/9/24 01:35, Fabiano Rosas wrote:
> The following changes since commit 4e66a08546a2588a4667766a1edab9caccf24ce3:
>
> Merge tag 'for-upstream' ofhttps://gitlab.com/bonzini/qemu into staging (2024-05-07 09:26:30 -0700)
>
> are available in the Git repository at:
>
> https://gitlab.com/farosas/qemu.git tags/migration-20240508-pull-request
>
> for you to fetch changes up to db8cb7b6e73690233bc7c6abbb90979af3a18143:
>
> hmp/migration: Fix "migrate" command's documentation (2024-05-08 09:22:37 -0300)
>
> ----------------------------------------------------------------
> Migration pull request
>
> - Will's WITH_QEMU_LOCK_GUARD cleanup
> - Vladimir's new exit-on-error parameter
> - Fabiano's removals and deprecations series
> (block migration and non-multifd compression removed)
> - Peter's documentation fix for HMP migrate command
>
> v2:
> - updated Peter's documentation fix.
Applied, thanks. Please update https://wiki.qemu.org/ChangeLog/9.1 as appropriate.
r~
prev parent reply other threads:[~2024-05-10 5:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 23:35 [PULL v2 00/13] Migration patches for 2024-05-08 Fabiano Rosas
2024-05-08 23:35 ` [PULL v2 01/13] migration/ram.c: API Conversion qemu_mutex_lock(), and qemu_mutex_unlock() to WITH_QEMU_LOCK_GUARD macro Fabiano Rosas
2024-05-08 23:35 ` [PULL v2 02/13] migration: move trace-point from migrate_fd_error to migrate_set_error Fabiano Rosas
2024-05-08 23:35 ` [PULL v2 03/13] migration: process_incoming_migration_co(): complete cleanup on failure Fabiano Rosas
2024-05-08 23:35 ` [PULL v2 04/13] migration: process_incoming_migration_co(): fix reporting s->error Fabiano Rosas
2024-05-08 23:35 ` [PULL v2 05/13] migration: process_incoming_migration_co(): rework error reporting Fabiano Rosas
2024-05-08 23:35 ` [PULL v2 06/13] qapi: introduce exit-on-error parameter for migrate-incoming Fabiano Rosas
2024-05-08 23:35 ` [PULL v2 07/13] migration: Remove 'skipped' field from MigrationStats Fabiano Rosas
2024-05-08 23:35 ` [PULL v2 08/13] migration: Remove 'inc' option from migrate command Fabiano Rosas
2024-05-08 23:35 ` [PULL v2 09/13] migration: Remove 'blk/-b' option from migrate commands Fabiano Rosas
2024-05-08 23:35 ` [PULL v2 10/13] migration: Remove block migration Fabiano Rosas
2024-05-08 23:35 ` [PULL v2 11/13] migration: Remove non-multifd compression Fabiano Rosas
2024-05-08 23:35 ` [PULL v2 12/13] migration: Deprecate fd: for file migration Fabiano Rosas
2024-05-08 23:35 ` [PULL v2 13/13] hmp/migration: Fix "migrate" command's documentation Fabiano Rosas
2024-05-10 5:38 ` Richard Henderson [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=0e971b27-102f-423d-9db2-95810a921ae3@linaro.org \
--to=richard.henderson@linaro.org \
--cc=farosas@suse.de \
--cc=peterx@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 read-only IMAP folder(s) and NNTP newsgroup(s).