qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Luiz Capitulino <lcapitulino@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: kwolf@redhat.com, wenchaoqemu@gmail.com, qemu-devel@nongnu.org,
	stefanha@redhat.com, pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH 2.1 0/2] Fix two recent event regressions
Date: Fri, 27 Jun 2014 12:55:51 -0400	[thread overview]
Message-ID: <20140627125551.5c732e70@redhat.com> (raw)
In-Reply-To: <1403876842-15926-1-git-send-email-armbru@redhat.com>

On Fri, 27 Jun 2014 15:47:20 +0200
Markus Armbruster <armbru@redhat.com> wrote:

> This series plus Paolo's "[PATCH for 2.1] qdev: correctly send
> DEVICE_DELETED for recursively-deleted devices" makes qemu-iotests
> check -qcow2 again pass for me.
> 
> Luiz offered to take it through his tree.

Kevin is going to take them via block tree:

Reviewed-by: Luiz Capitulino <lcapitulino@redhat.com>

> 
> Markus Armbruster (2):
>   blockjob: Fix recent BLOCK_JOB_READY regression
>   blockjob: Fix recent BLOCK_JOB_ERROR regression
> 
>  blockjob.c           | 8 ++++++--
>  qapi/block-core.json | 8 ++++++--
>  2 files changed, 12 insertions(+), 4 deletions(-)
> 

      parent reply	other threads:[~2014-06-27 18:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-27 13:47 [Qemu-devel] [PATCH 2.1 0/2] Fix two recent event regressions Markus Armbruster
2014-06-27 13:47 ` [Qemu-devel] [PATCH 2.1 1/2] blockjob: Fix recent BLOCK_JOB_READY regression Markus Armbruster
2014-06-27 16:28   ` Kevin Wolf
2014-06-27 16:42     ` Luiz Capitulino
2014-06-27 16:55     ` Markus Armbruster
2014-06-27 13:47 ` [Qemu-devel] [PATCH 2.1 2/2] blockjob: Fix recent BLOCK_JOB_ERROR regression Markus Armbruster
2014-06-27 16:31   ` Kevin Wolf
2014-06-27 16:20 ` [Qemu-devel] [PATCH 2.1 0/2] Fix two recent event regressions Benoît Canet
2014-06-27 16:55 ` Luiz Capitulino [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=20140627125551.5c732e70@redhat.com \
    --to=lcapitulino@redhat.com \
    --cc=armbru@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=wenchaoqemu@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 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).