qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, jsnow@redhat.com
Subject: [Qemu-devel] [PULL 0/2] Bitmaps patches
Date: Wed,  4 Jul 2018 02:33:53 -0400	[thread overview]
Message-ID: <20180704063355.25818-1-jsnow@redhat.com> (raw)

The following changes since commit 79c2b203a932db5882a3f328db53e5a448cd47f9:

  Merge remote-tracking branch 'remotes/kraxel/tags/vga-20180703-pull-request' into staging (2018-07-03 21:09:27 +0100)

are available in the Git repository at:

  https://github.com/jnsnow/qemu.git tags/bitmaps-pull-request

for you to fetch changes up to 58f72b965e9e1820d246329461216c4d13140122:

  dirty-bitmap: fix double lock on bitmap enabling (2018-07-04 02:12:49 -0400)

----------------------------------------------------------------
Pull request

----------------------------------------------------------------

Vladimir Sementsov-Ogievskiy (2):
  block/dirty-bitmap: add bdrv_enable_dirty_bitmap_locked
  dirty-bitmap: fix double lock on bitmap enabling

 block/dirty-bitmap.c           | 12 +++++++++---
 include/block/dirty-bitmap.h   |  1 +
 migration/block-dirty-bitmap.c |  4 ++--
 3 files changed, 12 insertions(+), 5 deletions(-)

-- 
2.14.4

             reply	other threads:[~2018-07-04  6:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-04  6:33 John Snow [this message]
2018-07-04  6:33 ` [Qemu-devel] [PULL 1/2] block/dirty-bitmap: add bdrv_enable_dirty_bitmap_locked John Snow
2018-07-04  6:33 ` [Qemu-devel] [PULL 2/2] dirty-bitmap: fix double lock on bitmap enabling John Snow
2018-07-05 13:25 ` [Qemu-devel] [PULL 0/2] Bitmaps patches Peter Maydell
  -- strict thread matches above, loose matches on Subject: below --
2019-05-01 20:25 John Snow
2019-05-01 20:25 ` John Snow
2019-05-02 12:12 ` Peter Maydell
2019-05-02 12:12   ` 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=20180704063355.25818-1-jsnow@redhat.com \
    --to=jsnow@redhat.com \
    --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 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).