public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat•com>
To: Liu Yu-B13201 <Yu.Liu@freescale•com>
Cc: linuxppc-dev@ozlabs•org, Yang Shi <yang.shi@windriver•com>,
	kvm-ppc@vger•kernel.org, hollisb@us•ibm.com, kvm@vger•kernel.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@zch01exm26.fsl.freescale.net>

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

  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
2009-07-02  3:09 ` [PATCH 1/2] KVM/PPC: Fix PPC KVM e500_tlb.c build error Liu Yu-B13201
2009-07-02 11:19   ` Avi Kivity [this message]
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@redhat$(echo .)com \
    --cc=Yu.Liu@freescale$(echo .)com \
    --cc=hollisb@us$(echo .)ibm.com \
    --cc=kvm-ppc@vger$(echo .)kernel.org \
    --cc=kvm@vger$(echo .)kernel.org \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    --cc=yang.shi@windriver$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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