From: Hollis Blanchard <hollisb@us.ibm.com>
To: Avi Kivity <avi@redhat.com>
Cc: kvm-ppc@vger.kernel.org, kvm <kvm@vger.kernel.org>
Subject: regression tests? (was Re: [PATCH] kvm-userspace: move x86
Date: Tue, 04 Nov 2008 15:18:06 +0000 [thread overview]
Message-ID: <1225811886.15410.6.camel@localhost.localdomain> (raw)
In-Reply-To: <49101FB7.3070000@redhat.com>
On Tue, 2008-11-04 at 12:11 +0200, Avi Kivity wrote:
> 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.
Avi, do you have a quick regression test you run before pushing new
patches? If so, we'd like to help you add PowerPC to that, if only to
detect build breaks like this one.
--
Hollis Blanchard
IBM Linux Technology Center
WARNING: multiple messages have this Message-ID (diff)
From: Hollis Blanchard <hollisb@us.ibm.com>
To: Avi Kivity <avi@redhat.com>
Cc: kvm-ppc@vger.kernel.org, kvm <kvm@vger.kernel.org>
Subject: regression tests? (was Re: [PATCH] kvm-userspace: move x86 specific calls introduced by device assignement to x86 files)
Date: Tue, 04 Nov 2008 09:18:06 -0600 [thread overview]
Message-ID: <1225811886.15410.6.camel@localhost.localdomain> (raw)
In-Reply-To: <49101FB7.3070000@redhat.com>
On Tue, 2008-11-04 at 12:11 +0200, Avi Kivity wrote:
> 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.
Avi, do you have a quick regression test you run before pushing new
patches? If so, we'd like to help you add PowerPC to that, if only to
detect build breaks like this one.
--
Hollis Blanchard
IBM Linux Technology Center
next prev parent reply other threads:[~2008-11-04 15:18 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 ` [PATCH] kvm-userspace: move x86 specific calls introduced by Avi Kivity
2008-11-04 10:11 ` [PATCH] kvm-userspace: move x86 specific calls introduced by device assignement to x86 files Avi Kivity
2008-11-04 15:18 ` Hollis Blanchard [this message]
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=1225811886.15410.6.camel@localhost.localdomain \
--to=hollisb@us.ibm.com \
--cc=avi@redhat.com \
--cc=kvm-ppc@vger.kernel.org \
--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 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.