From: Fam Zheng <famz@redhat.com>
To: qemu-devel@nongnu.org
Cc: stefanha@redhat.com
Subject: [Qemu-devel] [PULL 0/1] hbitmap fix for 2.8
Date: Tue, 29 Nov 2016 18:34:37 +0800 [thread overview]
Message-ID: <20161129103438.15955-1-famz@redhat.com> (raw)
The following changes since commit 00227fefd2059464cd2f59aed29944874c630e2f:
Update version for v2.8.0-rc1 release (2016-11-22 22:29:08 +0000)
are available in the git repository at:
git://github.com/famz/qemu.git tags/for-upstream
for you to fetch changes up to 6725f887acc023fc8850d62e1aaef083fdb4f3d4:
hbitmap: Fix shifts of constants by granularity (2016-11-29 17:46:36 +0800)
----------------------------------------------------------------
----------------------------------------------------------------
Max Reitz (1):
hbitmap: Fix shifts of constants by granularity
util/hbitmap.c | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
--
2.9.3
next reply other threads:[~2016-11-29 10:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 10:34 Fam Zheng [this message]
2016-11-29 10:34 ` [Qemu-devel] [PULL 1/1] hbitmap: Fix shifts of constants by granularity Fam Zheng
2016-11-29 14:15 ` [Qemu-devel] [PULL 0/1] hbitmap fix for 2.8 Stefan Hajnoczi
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=20161129103438.15955-1-famz@redhat.com \
--to=famz@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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).