From: John Snow <jsnow@redhat.com>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, jsnow@redhat.com
Subject: [Qemu-devel] [PULL 0/1] Bitmaps patches
Date: Wed, 7 Feb 2018 12:01:23 -0500 [thread overview]
Message-ID: <20180207170124.26704-1-jsnow@redhat.com> (raw)
The following changes since commit 0833df03f4206a6cf416fbb3d380fa95c8e61fba:
Merge remote-tracking branch 'remotes/dgilbert/tags/pull-migration-20180206a' into staging (2018-02-07 12:07:23 +0000)
are available in the Git repository at:
https://github.com/jnsnow/qemu.git tags/bitmaps-pull-request
for you to fetch changes up to 3260cdfffbf00f33923f5f9f6bef45932d7ac28b:
hbitmap: fix missing restore count when finish deserialization (2018-02-07 11:35:49 -0500)
----------------------------------------------------------------
----------------------------------------------------------------
Liang Li (1):
hbitmap: fix missing restore count when finish deserialization
util/hbitmap.c | 1 +
1 file changed, 1 insertion(+)
--
2.14.3
next reply other threads:[~2018-02-07 17:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-07 17:01 John Snow [this message]
2018-02-07 17:01 ` [Qemu-devel] [PULL 1/1] hbitmap: fix missing restore count when finish deserialization John Snow
2018-02-08 11:04 ` [Qemu-devel] [PULL 0/1] Bitmaps patches 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=20180207170124.26704-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).