From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: [Qemu-devel] [PATCH 2/2] virtio-blk: drop unused migration.h include
Date: Mon, 25 Jan 2016 13:33:21 +0000 [thread overview]
Message-ID: <1453728801-5398-3-git-send-email-stefanha@redhat.com> (raw)
In-Reply-To: <1453728801-5398-1-git-send-email-stefanha@redhat.com>
The migration blocker functionality is no longer necessary since
dataplane is now compatible with live migration. Drop the unused header
include.
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
---
This patch can be squashed into "virtio-blk: do not use vring in
dataplane".
---
hw/block/virtio-blk.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/hw/block/virtio-blk.c b/hw/block/virtio-blk.c
index 1106d13..3e34d35 100644
--- a/hw/block/virtio-blk.c
+++ b/hw/block/virtio-blk.c
@@ -20,7 +20,6 @@
#include "sysemu/blockdev.h"
#include "hw/virtio/virtio-blk.h"
#include "dataplane/virtio-blk.h"
-#include "migration/migration.h"
#include "block/scsi.h"
#ifdef __linux__
# include <scsi/sg.h>
--
2.5.0
next prev parent reply other threads:[~2016-01-25 13:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 13:33 [Qemu-devel] [PATCH 0/2] dataplane: RCU dirty memory bitmap for safe RAM hotplug Stefan Hajnoczi
2016-01-25 13:33 ` [Qemu-devel] [PATCH 1/2] memory: RCU ram_list.dirty_memory[] " Stefan Hajnoczi
2016-01-25 13:33 ` Stefan Hajnoczi [this message]
2016-01-25 13:46 ` [Qemu-devel] [PATCH 2/2] virtio-blk: drop unused migration.h include Paolo Bonzini
2016-01-28 10:40 ` [Qemu-devel] [PATCH 0/2] dataplane: RCU dirty memory bitmap for safe RAM hotplug Stefan Hajnoczi
2016-01-28 11:05 ` Paolo Bonzini
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=1453728801-5398-3-git-send-email-stefanha@redhat.com \
--to=stefanha@redhat.com \
--cc=pbonzini@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 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).