From: Anthony Liguori <anthony@codemonkey.ws>
To: Kevin Wolf <kwolf@redhat.com>
Cc: stefanha@gmail.com, qemu-devel@nongnu.org, lcapitulino@redhat.com
Subject: [Qemu-devel] Re: [PATCH 0.14/master v2 0/4] Error messages for unsupoorted image format features
Date: Thu, 10 Feb 2011 13:14:51 +0100 [thread overview]
Message-ID: <4D53D6BB.2090007@codemonkey.ws> (raw)
In-Reply-To: <1297336703-15632-1-git-send-email-kwolf@redhat.com>
On 02/10/2011 12:18 PM, Kevin Wolf wrote:
> With 0.15 we'll most likely get some incompatible image format extensions. This
> series prepares 0.14 to output more helpful messages if it stumbles over a too
> new image file.
>
> Kevin Wolf (4):
> qerror: Add QERR_UNKNOWN_BLOCK_FORMAT_FEATURE
> qcow2: Report error for version> 2
> qed: Report error for unsupported features
> qemu-img: Improve error messages for failed bdrv_open
>
Whole series:
Reviewed-by: Anthony Liguori <aliguori@us.ibm.com>
> block/qcow2.c | 13 +++++++++++--
> block/qed.c | 9 ++++++++-
> qemu-img.c | 10 +++++++---
> qerror.c | 5 +++++
> qerror.h | 3 +++
> 5 files changed, 34 insertions(+), 6 deletions(-)
>
>
prev parent reply other threads:[~2011-02-10 12:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-10 11:18 [Qemu-devel] [PATCH 0.14/master v2 0/4] Error messages for unsupoorted image format features Kevin Wolf
2011-02-10 11:18 ` [Qemu-devel] [PATCH v2 1/4] qerror: Add QERR_UNKNOWN_BLOCK_FORMAT_FEATURE Kevin Wolf
2011-02-10 11:18 ` [Qemu-devel] [PATCH v2 2/4] qcow2: Report error for version > 2 Kevin Wolf
2011-02-10 11:18 ` [Qemu-devel] [PATCH v2 3/4] qed: Report error for unsupported features Kevin Wolf
2011-02-10 12:07 ` [Qemu-devel] " Stefan Hajnoczi
2011-02-10 11:18 ` [Qemu-devel] [PATCH v2 4/4] qemu-img: Improve error messages for failed bdrv_open Kevin Wolf
2011-02-10 12:14 ` Anthony Liguori [this message]
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=4D53D6BB.2090007@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=kwolf@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.