From: Chen Gang <gang.chen.5i5j@gmail.com>
To: Liqin Chen <liqin.linux@gmail.com>, Lennox Wu <lennox.wu@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [PATCH] arch/score/Kconfig: Remain but disable STACKTRACE_SUPPORT
Date: Tue, 08 Jul 2014 15:43:47 +0800 [thread overview]
Message-ID: <53BBA133.9010104@gmail.com> (raw)
If enable STACKTRACE_SUPPORT, score has to implement save_stack_trace()
too. At present, it does not implement save_stack_trace(). So remain
but disable STACKTRACE_SUPPORT, just like um architecture has done.
LD init/built-in.o
kernel/built-in.o: In function `save_trace':
lockdep.c:(.text.save_trace+0x44): undefined reference to `save_stack_trace'
kernel/built-in.o: In function `match_held_lock':
lockdep.c:(.text.match_held_lock+0x78): undefined reference to `save_stack_trace'
kernel/built-in.o: In function `.L1144':
lockdep.c:(.text.lockdep_init_map+0x1a4): undefined reference to `save_stack_trace'
kernel/built-in.o: In function `.L1197':
lockdep.c:(.text.__lock_acquire+0x14c): undefined reference to `save_stack_trace'
kernel/built-in.o: In function `.L1856':
lockdep.c:(.text.__lock_set_class+0x160): undefined reference to `save_stack_trace'
kernel/built-in.o:(.text.lockdep_reset_lock+0xa0): more undefined references to `save_stack_trace' follow
make: *** [vmlinux] Error 1
Signed-off-by: Chen Gang <gang.chen.5i5j@gmail.com>
---
arch/score/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/score/Kconfig b/arch/score/Kconfig
index 4ac8cae..2ba8d05 100644
--- a/arch/score/Kconfig
+++ b/arch/score/Kconfig
@@ -76,7 +76,7 @@ config LOCKDEP_SUPPORT
def_bool y
config STACKTRACE_SUPPORT
- def_bool y
+ def_bool n
source "init/Kconfig"
--
1.9.2.459.g68773ac
reply other threads:[~2014-07-08 7:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=53BBA133.9010104@gmail.com \
--to=gang.chen.5i5j@gmail.com \
--cc=lennox.wu@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liqin.linux@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.