From: Stefan Hajnoczi <stefanha@gmail.com>
To: Alberto Garcia <berto@igalia.com>
Cc: Max Reitz <mreitz@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH v4 0/3] Add bdrv_get_device_or_node_name()
Date: Tue, 21 Apr 2015 14:47:47 +0100 [thread overview]
Message-ID: <20150421134747.GG16345@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <cover.1428485266.git.berto@igalia.com>
[-- Attachment #1: Type: text/plain, Size: 2164 bytes --]
On Wed, Apr 08, 2015 at 12:29:17PM +0300, Alberto Garcia wrote:
> This series contains a couple of minor changes suggested by Markus in
> the previous one. I removed the Reviewed-by line by Max in the
> modified patch even if the changes are small, hope that's ok.
>
> v4:
> - Fix documentation of the 'node-name' field in BLOCK_IMAGE_CORRUPTED.
> Its annotation is now (json-string, optional).
> - Clarify that the 'device' field can be empty even if it's always
> present for compatibility reasons.
>
> v3:
> - The node-name field in BLOCK_IMAGE_CORRUPTED is now Since: 2.4
> - Remove the QERR_ macros instead of updating them. The text message
> is adapted to each case where applicable, and 'device' is renamed to
> 'node' only where it makes sense.
>
> v2:
> - bdrv_get_device_or_node_name() includes a comment explaining its
> usage.
> - The error messages have been updated to say 'node' instead of
> 'device' where appropriate.
> - The BLOCK_IMAGE_CORRUPTED event has a new 'node-name' field.
>
> Regards,
>
> Berto
>
> Alberto Garcia (3):
> block: add bdrv_get_device_or_node_name()
> block: use bdrv_get_device_or_node_name() in error messages
> block: add 'node-name' field to BLOCK_IMAGE_CORRUPTED
>
> block.c | 33 +++++++++++++++++++++------------
> block/qcow.c | 8 ++++----
> block/qcow2.c | 10 +++++++---
> block/qed.c | 2 +-
> block/quorum.c | 5 +----
> block/snapshot.c | 12 ++++++------
> block/vdi.c | 6 +++---
> block/vhdx.c | 6 +++---
> block/vmdk.c | 8 ++++----
> block/vpc.c | 6 +++---
> block/vvfat.c | 7 ++++---
> blockdev.c | 9 +++++----
> docs/qmp/qmp-events.txt | 21 +++++++++++++--------
> include/block/block.h | 1 +
> include/qapi/qmp/qerror.h | 6 ------
> qapi/block-core.json | 17 +++++++++++------
> 16 files changed, 87 insertions(+), 70 deletions(-)
Thanks, applied to my block-next tree:
https://github.com/stefanha/qemu/commits/block-next
Stefan
[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-04-21 13:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 9:29 [Qemu-devel] [PATCH v4 0/3] Add bdrv_get_device_or_node_name() Alberto Garcia
2015-04-08 9:29 ` [Qemu-devel] [PATCH 1/3] block: add bdrv_get_device_or_node_name() Alberto Garcia
2015-04-08 16:32 ` Eric Blake
2015-04-08 9:29 ` [Qemu-devel] [PATCH 2/3] block: use bdrv_get_device_or_node_name() in error messages Alberto Garcia
2015-04-08 16:27 ` Eric Blake
2015-04-09 8:25 ` Alberto Garcia
2015-04-08 9:29 ` [Qemu-devel] [PATCH 3/3] block: add 'node-name' field to BLOCK_IMAGE_CORRUPTED Alberto Garcia
2015-04-08 23:32 ` Eric Blake
2015-04-09 7:30 ` Alberto Garcia
2015-04-15 13:24 ` Max Reitz
2015-04-21 13:47 ` Stefan Hajnoczi [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=20150421134747.GG16345@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=armbru@redhat.com \
--cc=berto@igalia.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--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).