qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: "Kevin Wolf" <kwolf@redhat.com>,
	"Eduardo Habkost" <ehabkost@redhat.com>,
	libvir-list@redhat.com, "Stefan Hajnoczi" <stefanha@gmail.com>,
	qemu-devel@nongnu.org, "Markus Armbruster" <armbru@redhat.com>,
	"Gerd Hoffmann" <kraxel@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Luiz Capitulino" <lcapitulino@redhat.com>,
	"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCHv3] qdev: DEVICE_DELETED event
Date: Thu, 7 Mar 2013 20:04:58 +0200	[thread overview]
Message-ID: <20130307180458.GA30633@redhat.com> (raw)
In-Reply-To: <87ehfrds8m.fsf@codemonkey.ws>

On Thu, Mar 07, 2013 at 11:39:21AM -0600, Anthony Liguori wrote:
> Markus Armbruster <armbru@redhat.com> writes:
> 
> > "Michael S. Tsirkin" <mst@redhat.com> writes:
> >
> >> libvirt has a long-standing bug: when removing the device,
> >> it can request removal but does not know when the
> >> removal completes. Add an event so we can fix this in a robust way.
> >
> > This is *v4*.  I think you should respin to avoid confusing Anthony's
> > tools.
> 
> Ack and thanks for pointing this out.  Please put a space before the v3
> too.
> 
> Regards,
> 
> Anthony Liguori

Do you need me to respin or can you apply this for now?

>   Recommend to delay the respin until the discussion we're having
> > in the v1 thread has run its course.

  reply	other threads:[~2013-03-07 18:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-07 16:48 [Qemu-devel] [PATCHv3] qdev: DEVICE_DELETED event Michael S. Tsirkin
2013-03-07 17:24 ` Markus Armbruster
2013-03-07 17:39   ` Anthony Liguori
2013-03-07 18:04     ` Michael S. Tsirkin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-03-07  9:49 Michael S. Tsirkin
2013-03-07 13:06 ` Andreas Färber

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=20130307180458.GA30633@redhat.com \
    --to=mst@redhat.com \
    --cc=afaerber@suse.de \
    --cc=aliguori@us.ibm.com \
    --cc=armbru@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=libvir-list@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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).