From: Avi Kivity <avi-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Hollis Blanchard <hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: kvm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
kvm-ppc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: e500 KVM build fixes for 2.6.29
Date: Thu, 15 Jan 2009 11:36:17 +0200 [thread overview]
Message-ID: <496F0391.5020200@redhat.com> (raw)
In-Reply-To: <1231951658-21108-1-git-send-email-hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Hollis Blanchard wrote:
> Avi, these patches fix build issues in the new e500 code. Please apply for
> 2.6.29. Thanks!
>
Applied for 2.6.30, but e500 isn't in 2.6.29?
--
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-01-15 9:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 16:47 e500 KVM build fixes for 2.6.29 Hollis Blanchard
2009-01-14 16:47 ` [PATCH 1/3] Subject: powerpc/fsl-booke: declare tlbcam_index for use in c Hollis Blanchard
2009-01-14 16:47 ` [PATCH 2/3] Subject: kvm: ppc: Fix e500 warnings and some spelling problems Hollis Blanchard
2009-01-14 16:47 ` [PATCH 3/3] Subject: kvm: ppc: Move to new TLB invalidate interface Hollis Blanchard
[not found] ` <1231951658-21108-1-git-send-email-hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-01-15 9:36 ` Avi Kivity [this message]
2009-01-15 17:19 ` e500 KVM build fixes for 2.6.29 Hollis Blanchard
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=496F0391.5020200@redhat.com \
--to=avi-h+wxahxf7alqt0dzr+alfa@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 \
/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