public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Ehrhardt Christian <ehrhardt@linux.vnet.ibm.com>
To: kvm@vger.kernel.org, avi@redhat.com
Cc: ehrhardt@linux.vnet.ibm.com, hollisb@us.ibm.com
Subject: [PATCH] [PATCH] kvm-userspace: fix io.h include merge confilict
Date: Mon, 10 Nov 2008 10:34:52 +0100	[thread overview]
Message-ID: <6b9c433aaf8dfa15e6fc.1226309692@HelionPrime> (raw)

From: Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>

These two patches went in with a conflict:
changeset:   16724:3ce8c651c948
user:        Ehrhardt Christian <ehrhardt@linux.vnet.ibm.com>
date:        Tue Nov 04 12:10:51 2008 +0200
summary:     kvm: qemu: move x86 specific calls introduced by device assignement to x86 files

changeset:   16723:c445df2fedcb
parent:      16675:cc9efba63149
user:        Xiantao Zhang <xiantao.zhang@intel.com>
date:        Mon Nov 03 17:56:15 2008 +0200
summary:     kvm: qemu: fix ia64 build breakage.

The final solution is to drop that io.h include in qemu-kvm.c completely.
After 16724 is applied there is no need for it in qemu-kvm.c anymore (16724
removed the original include).

Signed-off-by: Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>
---

[diffstat]

[diff]

diff --git a/qemu/qemu-kvm.c b/qemu/qemu-kvm.c
--- a/qemu/qemu-kvm.c
+++ b/qemu/qemu-kvm.c
@@ -1049,8 +1049,6 @@
     return kvm_unregister_coalesced_mmio(kvm_context, addr, size);
 }
 
-#include <sys/io.h>
-
 #ifdef USE_KVM_DEVICE_ASSIGNMENT
 void kvm_ioperm(CPUState *env, void *data)
 {

             reply	other threads:[~2008-11-10  9:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-10  9:34 Ehrhardt Christian [this message]
2008-11-10  9:46 ` [PATCH] [PATCH] kvm-userspace: fix io.h include merge confilict Avi Kivity

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=6b9c433aaf8dfa15e6fc.1226309692@HelionPrime \
    --to=ehrhardt@linux.vnet.ibm.com \
    --cc=avi@redhat.com \
    --cc=hollisb@us.ibm.com \
    --cc=kvm@vger.kernel.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