From: Kevin Wolf <kwolf@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, qemu-stable@nongnu.org, armbru@redhat.com,
stefanha@redhat.com, mreitz@redhat.com
Subject: [Qemu-devel] [PATCH v2 0/3] block: Don't probe for unknown backing file format
Date: Tue, 25 Nov 2014 18:12:39 +0100 [thread overview]
Message-ID: <1416935562-7760-1-git-send-email-kwolf@redhat.com> (raw)
v2:
- Added two patches to make the test case actually work properly and not
just by accident on my laptop. [Max]
- Fixed comment in test case [Max]
Kevin Wolf (3):
qcow2: Fix header extension size check
qcow2.py: Add required padding for header extensions
block: Don't probe for unknown backing file format
block.c | 7 +++---
block/qcow2.c | 2 +-
tests/qemu-iotests/080 | 2 ++
tests/qemu-iotests/080.out | 2 ++
tests/qemu-iotests/114 | 61 +++++++++++++++++++++++++++++++++++++++++++++
tests/qemu-iotests/114.out | 13 ++++++++++
tests/qemu-iotests/group | 1 +
tests/qemu-iotests/qcow2.py | 4 +++
8 files changed, 87 insertions(+), 5 deletions(-)
create mode 100755 tests/qemu-iotests/114
create mode 100644 tests/qemu-iotests/114.out
--
1.8.3.1
next reply other threads:[~2014-11-25 17:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-25 17:12 Kevin Wolf [this message]
2014-11-25 17:12 ` [Qemu-devel] [PATCH v2 1/3] qcow2: Fix header extension size check Kevin Wolf
2014-11-25 17:22 ` Max Reitz
2014-11-25 17:12 ` [Qemu-devel] [PATCH v2 2/3] qcow2.py: Add required padding for header extensions Kevin Wolf
2014-11-25 17:23 ` Max Reitz
2014-11-25 17:12 ` [Qemu-devel] [PATCH v2 3/3] block: Don't probe for unknown backing file format Kevin Wolf
2014-11-25 17:24 ` Max Reitz
2014-11-28 11:33 ` [Qemu-devel] [PATCH v2 0/3] " Stefan Hajnoczi
2014-12-02 10:23 ` Kevin Wolf
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=1416935562-7760-1-git-send-email-kwolf@redhat.com \
--to=kwolf@redhat.com \
--cc=armbru@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).