From: Daniel Walker <dwalker@mvista.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [git pull] scheduler updates for v2.6.27, phase #2
Date: Thu, 24 Jul 2008 15:12:40 -0400 [thread overview]
Message-ID: <1216926760.15470.14.camel@localhost.localdomain> (raw)
In-Reply-To: <20080724112412.GA12465@elte.hu>
On Thu, 2008-07-24 at 13:24 +0200, Ingo Molnar wrote:
> /me likes.
>
> applied to tip/sched/urgent, thanks guys.
Anyone for seconds?
kernel/sched.c:1107: warning: ‘init_hrtick’ defined but not used
and sched on ARM,
linus/kernel/sched.c:4227: warning: unsupported argument to ‘__builtin_return_address’
linus/kernel/sched.c:4206: warning: unsupported argument to ‘__builtin_return_address’
Also some ftrace on ARM,
linus/kernel/trace/trace_irqsoff.c:254: warning: unsupported argument to ‘__builtin_return_address’
linus/kernel/trace/trace_irqsoff.c:260: warning: unsupported argument to ‘__builtin_return_address’
linus/kernel/trace/trace_irqsoff.c:316: warning: unsupported argument to ‘__builtin_return_address’
linus/kernel/trace/trace_irqsoff.c:309: warning: unsupported argument to ‘__builtin_return_address’
linus/kernel/trace/trace_irqsoff.c:254: warning: unsupported argument to ‘__builtin_return_address’
linus/kernel/trace/trace_irqsoff.c:260: warning: unsupported argument to ‘__builtin_return_address’
The above also happens in trace_sched_wakeup.c .
Daniel
prev parent reply other threads:[~2008-07-24 19:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-21 15:38 [git pull] scheduler updates for v2.6.27, phase #2 Ingo Molnar
2008-07-21 16:31 ` Daniel Walker
2008-07-21 19:23 ` Peter Zijlstra
2008-07-21 20:16 ` Daniel Walker
2008-07-24 10:43 ` Peter Zijlstra
2008-07-24 11:09 ` Andrew Morton
2008-07-24 11:15 ` Peter Zijlstra
2008-07-24 11:24 ` Ingo Molnar
2008-07-24 19:12 ` Daniel Walker [this message]
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=1216926760.15470.14.camel@localhost.localdomain \
--to=dwalker@mvista.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.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