From: Avi Kivity <avi@redhat.com>
To: Ehrhardt Christian <ehrhardt@linux.vnet.ibm.com>
Cc: kvm-ppc@vger.kernel.org, kvm@vger.kernel.org, hollisb@us.ibm.com,
muli@il.ibm.com
Subject: Re: [PATCH] kvm-userspace: move x86 specific calls introduced by
Date: Tue, 04 Nov 2008 10:11:03 +0000 [thread overview]
Message-ID: <49101FB7.3070000@redhat.com> (raw)
In-Reply-To: <2e906c6317462fb1b551.1225732600@HelionPrime>
Ehrhardt Christian wrote:
> The device asignment patches added the x86 specific ioperm in qemu-kvm.
> This patch moves
> qemu-kvm.c:kvm_do_ioperm()
> to
> qemu-kvm-x86.c:kvm_arch_do_ioperm()
> The patch also changes the qemu-kvm header and the includes according to that.
>
>
Applied, thanks.
--
error compiling committee.c: too many arguments to function
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Ehrhardt Christian <ehrhardt@linux.vnet.ibm.com>
Cc: kvm-ppc@vger.kernel.org, kvm@vger.kernel.org, hollisb@us.ibm.com,
muli@il.ibm.com
Subject: Re: [PATCH] kvm-userspace: move x86 specific calls introduced by device assignement to x86 files
Date: Tue, 04 Nov 2008 12:11:03 +0200 [thread overview]
Message-ID: <49101FB7.3070000@redhat.com> (raw)
In-Reply-To: <2e906c6317462fb1b551.1225732600@HelionPrime>
Ehrhardt Christian wrote:
> The device asignment patches added the x86 specific ioperm in qemu-kvm.
> This patch moves
> qemu-kvm.c:kvm_do_ioperm()
> to
> qemu-kvm-x86.c:kvm_arch_do_ioperm()
> The patch also changes the qemu-kvm header and the includes according to that.
>
>
Applied, thanks.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-11-04 10:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-03 17:16 [PATCH] kvm-userspace: move x86 specific calls introduced by device Ehrhardt Christian
2008-11-03 17:16 ` [PATCH] kvm-userspace: move x86 specific calls introduced by device assignement to x86 files Ehrhardt Christian
2008-11-03 17:21 ` [PATCH] kvm-userspace: move x86 specific calls introduced by Hollis Blanchard
2008-11-03 17:21 ` [PATCH] kvm-userspace: move x86 specific calls introduced by device assignement to x86 files Hollis Blanchard
2008-11-04 10:11 ` Avi Kivity [this message]
2008-11-04 10:11 ` Avi Kivity
2008-11-04 15:18 ` regression tests? (was Re: [PATCH] kvm-userspace: move x86 Hollis Blanchard
2008-11-04 15:18 ` regression tests? (was Re: [PATCH] kvm-userspace: move x86 specific calls introduced by device assignement to x86 files) Hollis Blanchard
2008-11-04 15:25 ` regression tests? (was Re: [PATCH] kvm-userspace: move x86 specific Avi Kivity
2008-11-04 15:25 ` regression tests? (was Re: [PATCH] kvm-userspace: move x86 specific calls introduced by device assignement to x86 files) Avi Kivity
2008-11-04 15:39 ` regression tests? (was Re: [PATCH] kvm-userspace: move Hollis Blanchard
2008-11-04 15:39 ` regression tests? (was Re: [PATCH] kvm-userspace: move x86 specific calls introduced by device assignement to x86 files) Hollis Blanchard
2008-11-04 15:55 ` regression tests? (was Re: [PATCH] kvm-userspace: move x86 specific Avi Kivity
2008-11-04 15:55 ` regression tests? (was Re: [PATCH] kvm-userspace: move x86 specific calls introduced by device assignement to x86 files) 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=49101FB7.3070000@redhat.com \
--to=avi@redhat.com \
--cc=ehrhardt@linux.vnet.ibm.com \
--cc=hollisb@us.ibm.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=muli@il.ibm.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.