From: Eric Blake <eblake@redhat.com>
To: Juan Quintela <quintela@redhat.com>, qemu-devel@nongnu.org
Cc: dgilbert@redhat.com
Subject: Re: [Qemu-devel] [PATCH] migration: Make events a capability
Date: Mon, 3 Aug 2015 13:43:17 -0600 [thread overview]
Message-ID: <55BFC455.3010407@redhat.com> (raw)
In-Reply-To: <1436273249-20966-1-git-send-email-quintela@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1020 bytes --]
On 07/07/2015 06:47 AM, Juan Quintela wrote:
> Make check fails with events. THis is due to the parser/lexer that it
> uses. Just in case that they are more broken parsers, just only send
> events when there are capabilities.
>
> Signed-off-by: Juan Quintela <quintela@redhat.com>
> ---
> include/migration/migration.h | 1 +
> migration/migration.c | 20 ++++++++++++++++++--
> qapi-schema.json | 5 ++++-
> 3 files changed, 23 insertions(+), 3 deletions(-)
>
> +++ b/qapi-schema.json
> @@ -523,6 +523,9 @@
> # minimize migration traffic. The feature is disabled by default.
> # (since 2.4 )
Copying from pre-existing...
> #
> +# @events: generate events for each migration state change
> +# (since 2.4 )
...but the space before ) looks odd. A trivial followup patch may be in
order, but no need to hold up 2.4 for it.
--
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: 604 bytes --]
prev parent reply other threads:[~2015-08-03 19:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 12:47 [Qemu-devel] [PATCH] migration: Make events a capability Juan Quintela
2015-07-07 13:07 ` Dr. David Alan Gilbert
2015-08-03 19:43 ` Eric Blake [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=55BFC455.3010407@redhat.com \
--to=eblake@redhat.com \
--cc=dgilbert@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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).