From: Eric Blake <eblake@redhat.com>
To: Andrey Shinkevich <andrey.shinkevich@virtuozzo.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org
Cc: fam@euphon.net, armbru@redhat.com, mreitz@redhat.com,
kwolf@redhat.com, den@openvz.org, vsementsov@virtuozzo.com
Subject: Re: [Qemu-devel] [PATCH v10 1/3] bdrv_query_image_info Error parameter added
Date: Wed, 30 Jan 2019 12:03:03 -0600 [thread overview]
Message-ID: <2fabd78b-68cd-6ac6-0681-d6ad084c7c0b@redhat.com> (raw)
In-Reply-To: <1548870690-647481-2-git-send-email-andrey.shinkevich@virtuozzo.com>
[-- Attachment #1: Type: text/plain, Size: 504 bytes --]
On 1/30/19 11:51 AM, Andrey Shinkevich wrote:
> Inform a user in case qcow2_get_specific_info fails to obtain
> QCOW2 image specific information. This patch is preliminary to
> the print of bitmap information in the 'qemu-img info' output.
>
> Signed-off-by: Andrey Shinkevich <andrey.shinkevich@virtuozzo.com>
> ---
Reviewed-by: Eric Blake <eblake@redhat.com>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-01-30 18:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 17:51 [Qemu-devel] [PATCH v10 0/3] qemu-img info lists bitmap directory entries Andrey Shinkevich
2019-01-30 17:51 ` [Qemu-devel] [PATCH v10 1/3] bdrv_query_image_info Error parameter added Andrey Shinkevich
2019-01-30 18:03 ` Eric Blake [this message]
2019-01-30 17:51 ` [Qemu-devel] [PATCH v10 2/3] qemu-img info lists bitmap directory entries Andrey Shinkevich
2019-01-30 18:24 ` Eric Blake
2019-01-30 19:26 ` Andrey Shinkevich
2019-01-31 9:46 ` Vladimir Sementsov-Ogievskiy
2019-01-30 17:51 ` [Qemu-devel] [PATCH v10 3/3] qemu-img info: bitmaps extension new test 239 Andrey Shinkevich
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=2fabd78b-68cd-6ac6-0681-d6ad084c7c0b@redhat.com \
--to=eblake@redhat.com \
--cc=andrey.shinkevich@virtuozzo.com \
--cc=armbru@redhat.com \
--cc=den@openvz.org \
--cc=fam@euphon.net \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.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).