From: Steven Rostedt <rostedt@goodmis.org>
To: LKML <linux-kernel@vger.kernel.org>,
linux-s390 <linux-s390@vger.kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>,
Robert Richter <robert.richter@amd.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>
Subject: oprofile patch broke s390 build in tip/perf/core
Date: Wed, 21 Dec 2011 12:30:46 -0500 [thread overview]
Message-ID: <1324488646.5916.107.camel@gandalf.stny.rr.com> (raw)
Hi,
In doing my tests last night before sending out my patch series this
morning, I found that s390 build didn't work, but it wasn't due to my
patches. I removed all my patches and built with latest mainline (which
builds fine), and then merged the current tip/perf/core. The result
didn't build.
I kicked off a ktest git bisect with last night's Linus tree as good,
and with the merged in tip/perf/core as bad. It ended up with this patch
that broke the build (which looks like a likely suspect).
The break is this:
LD .tmp_vmlinux1
arch/s390/oprofile/built-in.o: In function `oprofile_arch_exit':
(.text+0x3f52): undefined reference to `oprofile_timer_exit'
make[1]: *** [.tmp_vmlinux1] Error 1
make: *** [sub-make] Error 2
The patch the bisect found that breaks the build is this:
commit 75c43a20b220f885c39ffa7cdbbb1191e257a9a9
Author: Robert Richter <robert.richter@amd.com>
Date: Fri Oct 14 15:46:10 2011 +0200
oprofile: Remove exit function for timer mode
Remove exit functions by moving init/exit code to oprofile's setup/
shutdown functions. Doing so the oprofile module exit code will be
easier and less error-prone.
Signed-off-by: Robert Richter <robert.richter@amd.com>
-- Steve
next reply other threads:[~2011-12-21 17:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-21 17:30 Steven Rostedt [this message]
2011-12-21 17:53 ` Robert Richter
2011-12-21 18:07 ` Steven Rostedt
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=1324488646.5916.107.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=robert.richter@amd.com \
--cc=schwidefsky@de.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®