From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: kvm@vger.kernel.org, kvm-ppc <kvm-ppc@vger.kernel.org>,
Liu Yu <yu.liu@freescale.com>
Subject: Re: [PATCH] KVM: PPC: E500 compile fix
Date: Sun, 17 Jan 2010 13:06:11 +0000 [thread overview]
Message-ID: <4B530B43.6070705@redhat.com> (raw)
In-Reply-To: <1263142908-8995-1-git-send-email-agraf@suse.de>
On 01/10/2010 07:01 PM, Alexander Graf wrote:
> While trying to compile an E500 vmlinux, I stumbled across a compilation bug
> that was obviously there before I touched any of the code. A trace point
> doesn't get the correct arguments.
>
> Since that shouldn't be any critical to the functionality of the code, my quick
> workaround is to #if 0 it out. I would very much appreciate someone fixing it
> properly though.
>
> Liu, it would be nice if you could be the one doing that.
>
Applied, thanks.
--
error compiling committee.c: too many arguments to function
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: kvm@vger.kernel.org, kvm-ppc <kvm-ppc@vger.kernel.org>,
Liu Yu <yu.liu@freescale.com>
Subject: Re: [PATCH] KVM: PPC: E500 compile fix
Date: Sun, 17 Jan 2010 15:06:11 +0200 [thread overview]
Message-ID: <4B530B43.6070705@redhat.com> (raw)
In-Reply-To: <1263142908-8995-1-git-send-email-agraf@suse.de>
On 01/10/2010 07:01 PM, Alexander Graf wrote:
> While trying to compile an E500 vmlinux, I stumbled across a compilation bug
> that was obviously there before I touched any of the code. A trace point
> doesn't get the correct arguments.
>
> Since that shouldn't be any critical to the functionality of the code, my quick
> workaround is to #if 0 it out. I would very much appreciate someone fixing it
> properly though.
>
> Liu, it would be nice if you could be the one doing that.
>
Applied, thanks.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-01-17 13:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-10 17:01 [PATCH] KVM: PPC: E500 compile fix Alexander Graf
2010-01-10 17:01 ` Alexander Graf
2010-01-11 7:05 ` Liu Yu-B13201
2010-01-11 7:05 ` Liu Yu-B13201
[not found] ` <0A1FE637C2C7E148B9573BB60CC630E56C3F14-bKEhWGtIRUJ4Lp7cDGe+DVjVikpgYyvb5NbjCUgZEJk@public.gmane.org>
2010-01-12 0:09 ` Alexander Graf
2010-01-12 0:09 ` Alexander Graf
2010-01-17 13:06 ` Avi Kivity [this message]
2010-01-17 13:06 ` Avi Kivity
2010-03-26 7:15 ` Bruce Majia
2010-03-26 7:15 ` Bruce Majia
2010-03-26 9:10 ` Alexander Graf
2010-03-26 9:10 ` Alexander Graf
[not found] ` <A306CC20-B0E4-4C6B-BAE4-A4F955E6663E-l3A5Bk7waGM@public.gmane.org>
2010-03-26 9:14 ` Liu Yu-B13201
2010-03-26 9:14 ` Liu Yu-B13201
2010-03-26 10:40 ` Bruce Majia
2010-03-26 10:40 ` Bruce Majia
2010-03-26 10:50 ` Alexander Graf
2010-03-26 10:50 ` Alexander Graf
[not found] ` <272B4229-9AC7-4D29-820F-5F958D4CC71C-l3A5Bk7waGM@public.gmane.org>
2010-03-26 11:20 ` Bruce Majia
2010-03-26 11:20 ` Bruce Majia
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=4B530B43.6070705@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=yu.liu@freescale.com \
/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.