qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Eric Blake <eblake@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PULL 0/1] bitmaps patches for 2020-07-17 [-rc1]
Date: Sat, 18 Jul 2020 23:58:48 +0100	[thread overview]
Message-ID: <CAFEAcA80KdFODWRpa2fOt71B7kfqKNUpA-N=D+8LcE_UxAOJSA@mail.gmail.com> (raw)
In-Reply-To: <20200717151446.655571-1-eblake@redhat.com>

On Fri, 17 Jul 2020 at 16:17, Eric Blake <eblake@redhat.com> wrote:
>
> The following changes since commit 151f76c689b1ff4c2c59e6d8469a0d4fe5346f55:
>
>   Merge remote-tracking branch 'remotes/ehabkost/tags/x86-next-pull-request' into staging (2020-07-16 21:46:18 +0100)
>
> are available in the Git repository at:
>
>   https://repo.or.cz/qemu/ericb.git tags/pull-bitmaps-2020-07-17
>
> for you to fetch changes up to 7cb015197b383a62f5729d2c92b1050db0185c1c:
>
>   migration/block-dirty-bitmap: fix add_bitmaps_to_list (2020-07-17 08:18:51 -0500)
>
> I had been waiting to see if I had more than one patch to bundle, but
> given that we are now coming up on -rc1 and this is a bugfix, it's time
> for the pull request of this in isolation.
>
> ----------------------------------------------------------------
> bitmaps patches for 2020-07-17
>
> - improve corner-case of bitmap migration
>
> ----------------------------------------------------------------
> Vladimir Sementsov-Ogievskiy (1):
>       migration/block-dirty-bitmap: fix add_bitmaps_to_list


Applied, thanks.

Please update the changelog at https://wiki.qemu.org/ChangeLog/5.1
for any user-visible changes.

-- PMM


      parent reply	other threads:[~2020-07-18 22:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-17 15:14 [PULL 0/1] bitmaps patches for 2020-07-17 [-rc1] Eric Blake
2020-07-17 15:14 ` [PULL 1/1] migration/block-dirty-bitmap: fix add_bitmaps_to_list Eric Blake
2020-07-18 22:58 ` 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='CAFEAcA80KdFODWRpa2fOt71B7kfqKNUpA-N=D+8LcE_UxAOJSA@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=eblake@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).