From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: kosaki.motohiro@jp.fujitsu.com,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-next@vger.kernel.org, Tejun Heo <tj@kernel.org>
Subject: Re: linux-next: tracing tree build failure
Date: Tue, 10 Mar 2009 11:16:37 +0900 (JST) [thread overview]
Message-ID: <20090310111435.A486.A69D9226@jp.fujitsu.com> (raw)
In-Reply-To: <20090310115509.328da465.sfr@canb.auug.org.au>
Hi Stephen,
> Hi all,
>
> Today's linux-next build (x86_64 allmodconfig) failed like this:
>
> kernel/trace/trace_functions_graph.c: In function 'graph_trace_close':
> kernel/trace/trace_functions_graph.c:836: error: implicit declaration of function 'percpu_free'
>
> The direct cause is commit 422d3c7a577b15e1384c9d4e72a9540896b685fa
> ("tracing: current tip/master can't enable ftrace") from the tracing tree
> which exposed an interaction between commit
> f2a8205c4ef1af917d175c36a4097ae5587791c8 ("percpu: kill percpu_alloc()
> and friends") from the tip-core tree and commit
> 9005f3ebebfcfe9ccd731d16c468907a35ac1f9a ("tracing/function-graph-tracer:
> various fixes and features") from the tracing tree.
>
> I have reverted commit 422d3c7a577b15e1384c9d4e72a9540896b685fa for
> today. (As a side note, that commit has no Signed-off-by ...)
I checked latest -tip tree and I found Ingo fixed this issue by following commit.
Could you please try to pull latest tip tree?
commit 56bc29b4b8e188275f52cd5270bcf54f22cfc92b
Author: Ingo Molnar <mingo@elte.hu>
Date: Thu Mar 5 22:04:39 2009 +0100
merge conflict resolutions
next prev parent reply other threads:[~2009-03-10 2:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-10 0:55 linux-next: tracing tree build failure Stephen Rothwell
2009-03-10 1:49 ` Tejun Heo
2009-03-10 9:10 ` Ingo Molnar
2009-03-10 2:16 ` KOSAKI Motohiro [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-03-26 1:14 Stephen Rothwell
2009-03-26 1:37 ` Masami Hiramatsu
2009-03-26 7:54 ` Ingo Molnar
2009-03-26 8:04 ` Stephen Rothwell
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=20090310111435.A486.A69D9226@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=hpa@zytor.com \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--cc=tj@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;
as well as URLs for NNTP newsgroup(s).