From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] ia64, xen: compilation fix caused by
Date: Thu, 15 Jan 2009 08:54:03 +0000 [thread overview]
Message-ID: <1232009643.30152.6.camel@localhost> (raw)
In-Reply-To: <20090115061655.GM1565%yamahata@valinux.co.jp>
On Thu, 2009-01-15 at 15:16 +0900, Isaku Yamahata wrote:
> This patch fixes the following errors caused by
> 79741dd35713ff4f6fd0eafd59fa94e8a4ba922d which changed
> the prototypes of account_steal_time() and account_idle_time().
>
> > CC arch/ia64/xen/time.o
> > arch/ia64/xen/time.c: In function 'consider_steal_time':
> > arch/ia64/xen/time.c:132: warning: passing argument 1 of 'account_steal_time' makes integer from pointer without a cast
> > arch/ia64/xen/time.c:132: error: too many arguments to function 'account_steal_time'
> > arch/ia64/xen/time.c:133: warning: passing argument 1 of 'account_steal_time' makes integer from pointer without a cast
> > arch/ia64/xen/time.c:133: error: too many arguments to function 'account_steal_time'
>
> Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>
> Signed-off-by: Isaku Yamahata <yamahata@valinux.co.jp>
Sorry, somehow I managed to miss this callsite for account_steal_time,
probably because it has not been present with 2.6.27 which is the
version I used to create the initial patch series.
I assume that this patch will be pushed via the ia64 patch queue, no?
--
blue skies,
Martin.
"Reality continues to ruin my life." - Calvin.
next prev parent reply other threads:[~2009-01-15 8:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-15 6:16 [PATCH] ia64, xen: compilation fix caused by 79741dd35713ff4f6fd0eafd59fa94e8a4ba922d Isaku Yamahata
2009-01-15 8:54 ` Martin Schwidefsky [this message]
2009-01-15 10:32 ` Isaku Yamahata
2009-01-15 18:24 ` [PATCH] ia64, xen: compilation fix caused by Luck, Tony
2009-01-16 3:39 ` [PATCH] ia64, xen: compilation fix caused by 79741dd35713ff4f6fd0eafd59fa94e8a4ba922d Isaku Yamahata
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=1232009643.30152.6.camel@localhost \
--to=schwidefsky@de.ibm.com \
--cc=linux-ia64@vger.kernel.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