All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-devel@nongnu.org, dgilbert@redhat.com
Subject: Re: [Qemu-devel] [PATCH 4/5] migration: Disable hotplug/unplug during migration
Date: Tue, 18 Apr 2017 21:30:06 +0200	[thread overview]
Message-ID: <87shl5h5tt.fsf@secure.mitica> (raw)
In-Reply-To: <76d42218-b542-4136-af87-5c0bc4d4afac@redhat.com> (Eric Blake's message of "Thu, 6 Apr 2017 09:09:10 -0500")

Eric Blake <eblake@redhat.com> wrote:
> On 04/06/2017 08:13 AM, Juan Quintela wrote:
>> Until we have reviewed what can/can't be hotplug during migration,
>
> s/hotplug/hotplugged/
>
>> disable it.  We can enable it later for the things that we know that
>> work.  For instance, memory hotplug during postcopy don't work
>
> s/don't/doesn't/

Fixed the three typos, thanks.

  reply	other threads:[~2017-04-18 19:30 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
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 [this message]
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=87shl5h5tt.fsf@secure.mitica \
    --to=quintela@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=eblake@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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.