From: Avi Kivity <avi-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Liu Yu-B13201 <Yu.Liu-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Cc: Yang Shi <yang.shi-CWA4WttNNZF54TAoqtyWWQ@public.gmane.org>,
hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org,
kvm-ppc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
kvm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linuxppc-dev-mnsaURCQ41sdnm+yROfE0A@public.gmane.org
Subject: Re: [PATCH 1/2] KVM/PPC: Fix PPC KVM e500_tlb.c build error
Date: Thu, 02 Jul 2009 14:19:32 +0300 [thread overview]
Message-ID: <4A4C97C4.9090908@redhat.com> (raw)
In-Reply-To: <0A1FE637C2C7E148B9573BB60CC630E531C59D-bKEhWGtIRUJ4Lp7cDGe+DVjVikpgYyvb5NbjCUgZEJk@public.gmane.org>
On 07/02/2009 06:09 AM, Liu Yu-B13201 wrote:
> This fix is already accepted in kvm.git
>
What about the other? Is it needed?
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe kvm-ppc" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-07-02 11:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-02 2:55 [PATCH 1/2] KVM/PPC: Fix PPC KVM e500_tlb.c build error Yang Shi
2009-07-02 2:55 ` [PATCH 2/2] KVM/PPC: Fix kvm_main.c build error for PPC KVM Yang Shi
[not found] ` <47a7508d4561874c1a052cebe1b7f42b19831393.1246502441.git.yang.shi-CWA4WttNNZF54TAoqtyWWQ@public.gmane.org>
2009-07-02 3:09 ` [PATCH 1/2] KVM/PPC: Fix PPC KVM e500_tlb.c build error Liu Yu-B13201
[not found] ` <0A1FE637C2C7E148B9573BB60CC630E531C59D-bKEhWGtIRUJ4Lp7cDGe+DVjVikpgYyvb5NbjCUgZEJk@public.gmane.org>
2009-07-02 11:19 ` Avi Kivity [this message]
[not found] ` <4A4C97C4.9090908-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-07-03 1:35 ` Liu Yu-B13201
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=4A4C97C4.9090908@redhat.com \
--to=avi-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=Yu.Liu-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
--cc=hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
--cc=kvm-ppc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=kvm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linuxppc-dev-mnsaURCQ41sdnm+yROfE0A@public.gmane.org \
--cc=yang.shi-CWA4WttNNZF54TAoqtyWWQ@public.gmane.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