From: Peter Maydell <peter.maydell@linaro.org>
To: "Dr. David Alan Gilbert (git)" <dgilbert@redhat.com>
Cc: leobras.c@gmail.com, Li Zhijian <lizhijian@cn.fujitsu.com>,
huangy81@chinatelecom.cn, QEMU Developers <qemu-devel@nongnu.org>,
Peter Xu <peterx@redhat.com>,
pabeni@redhat.com
Subject: Re: [PULL 0/9] migration queue
Date: Wed, 9 Jun 2021 17:56:40 +0100 [thread overview]
Message-ID: <CAFEAcA801yf-3ocAhQxTipp6+8AuMygbdeCHmkENHdjSHUUYoQ@mail.gmail.com> (raw)
In-Reply-To: <20210609144512.211746-1-dgilbert@redhat.com>
On Wed, 9 Jun 2021 at 15:47, Dr. David Alan Gilbert (git)
<dgilbert@redhat.com> wrote:
>
> From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
>
> The following changes since commit a4716fd8d7c877185652f5f8e25032dc7699d51b:
>
> Merge remote-tracking branch 'remotes/alistair/tags/pull-riscv-to-apply-20210608-1' into staging (2021-06-08 13:54:23 +0100)
>
> are available in the Git repository at:
>
> https://gitlab.com/dagrh/qemu.git tags/pull-migration-20210609a
>
> for you to fetch changes up to a4a571d97866d056787d7a654be5792765be8a60:
>
> hmp: Add "calc_dirty_rate" and "info dirty_rate" cmds (2021-06-08 20:18:26 +0100)
>
> ----------------------------------------------------------------
> Migration pull for 2021-06-09
>
> Yank crash fix from Leo
> RDMA fix from Li
> mptcp support from me
> dirty-rate changes from Hyman and Peter
>
> (Note I've switched to the gitlab I've been using for virtiofs pulls)
>
> Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Applied, thanks.
Please update the changelog at https://wiki.qemu.org/ChangeLog/6.1
for any user-visible changes.
-- PMM
next prev parent reply other threads:[~2021-06-09 16:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-09 14:45 [PULL 0/9] migration queue Dr. David Alan Gilbert (git)
2021-06-09 14:45 ` [PULL 1/9] yank: Unregister function when using TLS migration Dr. David Alan Gilbert (git)
2021-06-14 5:14 ` Philippe Mathieu-Daudé
2021-06-15 21:17 ` Leonardo Brás
2021-06-09 14:45 ` [PULL 2/9] migration/rdma: Fix cm event use after free Dr. David Alan Gilbert (git)
2021-06-09 14:45 ` [PULL 3/9] channel-socket: Only set CLOEXEC if we have space for fds Dr. David Alan Gilbert (git)
2021-06-09 14:45 ` [PULL 4/9] io/net-listener: Call the notifier during finalize Dr. David Alan Gilbert (git)
2021-06-09 14:45 ` [PULL 5/9] migration: Add cleanup hook for inwards migration Dr. David Alan Gilbert (git)
2021-06-09 14:45 ` [PULL 6/9] migration/socket: Close the listener at the end Dr. David Alan Gilbert (git)
2021-06-09 14:45 ` [PULL 7/9] sockets: Support multipath TCP Dr. David Alan Gilbert (git)
2021-06-09 14:45 ` [PULL 8/9] migration/dirtyrate: make sample page count configurable Dr. David Alan Gilbert (git)
2021-06-09 14:45 ` [PULL 9/9] hmp: Add "calc_dirty_rate" and "info dirty_rate" cmds Dr. David Alan Gilbert (git)
2021-06-09 16:56 ` Peter Maydell [this message]
2021-06-14 22:06 ` [PULL 0/9] migration queue no-reply
-- strict thread matches above, loose matches on Subject: below --
2020-03-25 13:16 Dr. David Alan Gilbert (git)
2020-03-26 10:46 ` Peter Maydell
2019-09-25 15:01 Dr. David Alan Gilbert (git)
2019-09-26 15:13 ` 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=CAFEAcA801yf-3ocAhQxTipp6+8AuMygbdeCHmkENHdjSHUUYoQ@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=dgilbert@redhat.com \
--cc=huangy81@chinatelecom.cn \
--cc=leobras.c@gmail.com \
--cc=lizhijian@cn.fujitsu.com \
--cc=pabeni@redhat.com \
--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 NNTP newsgroup(s).