From: Max Reitz <mreitz@redhat.com>
To: qemu-block@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-devel@nongnu.org, Max Reitz <mreitz@redhat.com>
Subject: [Qemu-devel] [PATCH v3 0/2] qcow2: Make size_to_clusters() return uint64_t
Date: Mon, 14 Sep 2015 16:39:46 +0200 [thread overview]
Message-ID: <1442241588-25672-1-git-send-email-mreitz@redhat.com> (raw)
Some callers actually expected that function to return uint64_t. As it
turns out, it doesn't. Fix that.
v3:
- Patch 1: Fix build for sizeof(void *) < 8 machines [Peter]
git-backport-diff against v2:
Key:
[----] : patches are identical
[####] : number of functional differences between upstream/downstream patch
[down] : patch is downstream-only
The flags [FC] indicate (F)unctional and (C)ontextual differences, respectively
001/2:[0002] [FC] 'qcow2: Make size_to_clusters() return uint64_t'
002/2:[----] [--] 'iotests: Add test for checking large image files'
Max Reitz (2):
qcow2: Make size_to_clusters() return uint64_t
iotests: Add test for checking large image files
block/qcow2-cluster.c | 30 ++++++++++++-------
block/qcow2-refcount.c | 12 +++++---
block/qcow2.h | 6 ++--
tests/qemu-iotests/138 | 73 ++++++++++++++++++++++++++++++++++++++++++++++
tests/qemu-iotests/138.out | 9 ++++++
tests/qemu-iotests/group | 1 +
6 files changed, 113 insertions(+), 18 deletions(-)
create mode 100755 tests/qemu-iotests/138
create mode 100644 tests/qemu-iotests/138.out
--
2.5.2
next reply other threads:[~2015-09-14 14:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-14 14:39 Max Reitz [this message]
2015-09-14 14:39 ` [Qemu-devel] [PATCH v3 1/2] qcow2: Make size_to_clusters() return uint64_t Max Reitz
2015-09-14 14:39 ` [Qemu-devel] [PATCH v3 2/2] iotests: Add test for checking large image files Max Reitz
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=1442241588-25672-1-git-send-email-mreitz@redhat.com \
--to=mreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.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).