From: Avi Kivity <avi@redhat.com>
To: ehrhardt@linux.vnet.ibm.com
Cc: hollisb@us.ibm.com, kvm@vger.kernel.org, kvm-ppc@vger.kernel.org,
qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH 0/3] kvm-userspace: kvmppc: fix build for ppc v2
Date: Thu, 02 Oct 2008 15:57:30 +0300 [thread overview]
Message-ID: <48E4C53A.8040009@redhat.com> (raw)
In-Reply-To: <1222756604-10899-1-git-send-email-ehrhardt@linux.vnet.ibm.com>
ehrhardt@linux.vnet.ibm.com wrote:
> From: Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>
>
> *update
> Short after resending v1 I realized that I forgot to put Avi and
> qemu-devel@nongnu.org (for 2/3) on cc. I also updated the header text in 1/3 a
> bit and verified my hostlongbits proposal on recent cross toolchain versions
> because there was a question about that.
>
> Updating and testing kvm-userspace for ppc after a too long time brought up
> some issues fixed in this series.
>
> The patches are small and their description should be comprehendible. Due to
> the fact that most of the issues where build time issues I also started to
> discuss about/establish some kind of automated build test for us that should
> allow us to find such things faster.
> Let me know if qumranet has such a process for x86 already and I should help
> you to include powerpc.
>
> [patches in series]
> [PATCH 1/3] kvm-userspace: kvmppc: fix file header in libkvm-powerpc.c
> [PATCH 2/3] kvm-userspace: kvmppc: fix hostlonbits detection when cross compiling
> [PATCH 3/3] kvm-userspace: kvmppc: fix building userspace for powerpc
>
Applied 1 and 3, thanks. 2 appears to have already been merged via qemu
upstream.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2008-10-02 13:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-30 6:36 [Qemu-devel] [PATCH 0/3] kvm-userspace: kvmppc: fix build for ppc v2 ehrhardt
2008-09-30 14:19 ` [Qemu-devel] " Hollis Blanchard
2008-10-02 12:57 ` Avi Kivity [this message]
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=48E4C53A.8040009@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=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).