From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Thomas Gleixner <tglx@linutronix•de>, Ingo Molnar <mingo@elte•hu>,
"H. Peter Anvin" <hpa@zytor•com>
Cc: linux-next@vger•kernel.org, Tejun Heo <tj@kernel•org>,
KOSAKI Motohiro <kosaki.motohiro@jp•fujitsu.com>
Subject: linux-next: tracing tree build failure
Date: Tue, 10 Mar 2009 11:55:09 +1100 [thread overview]
Message-ID: <20090310115509.328da465.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 932 bytes --]
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 ...)
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2009-03-10 0:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-10 0:55 Stephen Rothwell [this message]
2009-03-10 1:49 ` linux-next: tracing tree build failure Tejun Heo
2009-03-10 9:10 ` Ingo Molnar
2009-03-10 2:16 ` KOSAKI Motohiro
-- 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=20090310115509.328da465.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=hpa@zytor$(echo .)com \
--cc=kosaki.motohiro@jp$(echo .)fujitsu.com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mingo@elte$(echo .)hu \
--cc=tglx@linutronix$(echo .)de \
--cc=tj@kernel$(echo .)org \
/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