From: Markus Armbruster <armbru@redhat.com>
To: Juan Quintela <quintela@redhat.com>
Cc: qemu-devel@nongnu.org, dgilbert@redhat.com
Subject: Re: [Qemu-devel] [PATCH 3/5] qdev: Move qdev_unplug() to qdev-monitor.c
Date: Tue, 11 Apr 2017 13:29:46 +0200 [thread overview]
Message-ID: <87a87nb2s5.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <20170406131326.2418-4-quintela@redhat.com> (Juan Quintela's message of "Thu, 6 Apr 2017 15:13:24 +0200")
Juan Quintela <quintela@redhat.com> writes:
> It is not used by linux-user, otherwise I need to to create one stub
> for migration_is_idle() on following patch.
>
> Signed-off-by: Juan Quintela <quintela@redhat.com>
> ---
> hw/core/qdev.c | 34 ----------------------------------
> qdev-monitor.c | 34 ++++++++++++++++++++++++++++++++++
> 2 files changed, 34 insertions(+), 34 deletions(-)
Makes sense because its buddy qdev_device_add() is already in
qdev-monitor.c.
Reviewed-by: Markus Armbruster <armbru@redhat.com>
next prev parent reply other threads:[~2017-04-11 11:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-06 13:13 [Qemu-devel] [PATCH v2 0/5] Disable hotplug during migration Juan Quintela
2017-04-06 13:13 ` [Qemu-devel] [PATCH 1/5] qdev: qdev_hotplug is really a bool Juan Quintela
2017-04-06 13:46 ` Eric Blake
2017-04-06 16:39 ` Philippe Mathieu-Daudé
2017-04-06 13:13 ` [Qemu-devel] [PATCH 2/5] qdev: Export qdev_hot_removed Juan Quintela
2017-04-06 14:05 ` Eric Blake
2017-04-11 11:27 ` Markus Armbruster
2017-04-06 13:13 ` [Qemu-devel] [PATCH 3/5] qdev: Move qdev_unplug() to qdev-monitor.c Juan Quintela
2017-04-06 14:07 ` Eric Blake
2017-04-11 11:29 ` Markus Armbruster [this message]
2017-04-06 13:13 ` [Qemu-devel] [PATCH 4/5] migration: Disable hotplug/unplug during migration Juan Quintela
2017-04-06 14:09 ` Eric Blake
2017-04-18 19:30 ` Juan Quintela
2017-04-06 13:13 ` [Qemu-devel] [PATCH 5/5] ram: Remove migration_bitmap_extend() Juan Quintela
2017-04-06 14:09 ` Eric Blake
2017-04-10 8:22 ` [Qemu-devel] [PATCH v2 0/5] Disable hotplug during migration Hailiang Zhang
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=87a87nb2s5.fsf@dusky.pond.sub.org \
--to=armbru@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.