From: Stefan Hajnoczi <stefanha@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: aliguori@amazon.com, qemu-devel@nongnu.org, stefanha@redhat.com,
afaerber@suse.de
Subject: Re: [Qemu-devel] [PATCH regression] virtio: add back call to virtio_bus_device_unplugged
Date: Fri, 3 Jan 2014 18:50:21 +0800 [thread overview]
Message-ID: <20140103105021.GG1483@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1387565331-15730-1-git-send-email-pbonzini@redhat.com>
On Fri, Dec 20, 2013 at 07:48:51PM +0100, Paolo Bonzini wrote:
> This got lost in a rebase.
>
> Reported-by: Stefan Hajnoczi <stefanha@redhat.com>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> hw/virtio/virtio.c | 2 ++
> 1 file changed, 2 insertions(+)
Makes qemu-iotests happy again.
Thanks, applied to my block-next tree:
https://github.com/stefanha/qemu/commits/block-next
Stefan
prev parent reply other threads:[~2014-01-03 10:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-20 18:48 [Qemu-devel] [PATCH regression] virtio: add back call to virtio_bus_device_unplugged Paolo Bonzini
2014-01-03 10:50 ` 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=20140103105021.GG1483@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=afaerber@suse.de \
--cc=aliguori@amazon.com \
--cc=pbonzini@redhat.com \
--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).