From: Eric Blake <eblake@redhat.com>
To: Max Reitz <mreitz@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qmp: Documentation for BLOCK_IMAGE_CORRUPTED
Date: Tue, 03 Sep 2013 07:39:22 -0600 [thread overview]
Message-ID: <5225E68A.4090307@redhat.com> (raw)
In-Reply-To: <1378126884-9544-1-git-send-email-mreitz@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1108 bytes --]
On 09/02/2013 07:01 AM, Max Reitz wrote:
> Add an appropriate entry describing this event and its parameters into
> qmp-events.txt.
>
> Signed-off-by: Max Reitz <mreitz@redhat.com>
> ---
> Follow-up to:
> - Add metadata overlap checks (series, v5); particularly patch 2
> (qcow2: Metadata overlap checks)
> ---
> QMP/qmp-events.txt | 22 ++++++++++++++++++++++
> 1 file changed, 22 insertions(+)
>
> diff --git a/QMP/qmp-events.txt b/QMP/qmp-events.txt
> index 39b6016..6ff74d6 100644
> --- a/QMP/qmp-events.txt
> +++ b/QMP/qmp-events.txt
> @@ -478,3 +478,25 @@ Example:
>
> { "event": "GUEST_PANICKED",
> "data": { "action": "pause" } }
> +
> +BLOCK_IMAGE_CORRUPTED
> +---------------------
The content is fine, but the location is not. We are trying to keep
this file sorted by event name, so this belongs between BALLOON_CHANGE
and BLOCK_IO_ERROR.
As sorting is trivial, you can add this to your v2:
Reviewed-by: Eric Blake <eblake@redhat.com>
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]
next prev parent reply other threads:[~2013-09-03 13:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-02 13:01 [Qemu-devel] [PATCH] qmp: Documentation for BLOCK_IMAGE_CORRUPTED Max Reitz
2013-09-03 13:39 ` Eric Blake [this message]
2013-09-03 13:51 ` 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=5225E68A.4090307@redhat.com \
--to=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--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).