From: Yang Shi <yang.shi@linaro.org>
To: linux-kernel@vger.kernel.org
Cc: uclinux-h8-devel@lists.sourceforge.jp,
ysato@users.sourceforge.jp, hskinnemoen@gmail.com,
egtvedt@samfundet.no, linux-hexagon@vger.kernel.org,
rkuo@codeaurora.org, mingo@redhat.com, yang.shi@linaro.org
Subject: [PATCH 1/4] m32r: remove redundant FRAME_POINTER kconfig option
Date: Mon, 9 Nov 2015 11:21:15 -0800 [thread overview]
Message-ID: <1447096878-13519-2-git-send-email-yang.shi@linaro.org> (raw)
In-Reply-To: <1447096878-13519-1-git-send-email-yang.shi@linaro.org>
FRAME_POINTER is defined in lib/Kconfig.debug, it is unnecessary to redefine
it in arch/m32r/Kconfig.debug. Actually, the one defined in arch directory
is never used.
Signed-off-by: Yang Shi <yang.shi@linaro.org>
---
arch/m32r/Kconfig.debug | 8 --------
1 file changed, 8 deletions(-)
diff --git a/arch/m32r/Kconfig.debug b/arch/m32r/Kconfig.debug
index 6c612b7..a991aeb2 100644
--- a/arch/m32r/Kconfig.debug
+++ b/arch/m32r/Kconfig.debug
@@ -10,12 +10,4 @@ config DEBUG_PAGEALLOC
This results in a large slowdown, but helps to find certain types
of memory corruptions.
-config FRAME_POINTER
- bool "Compile the kernel with frame pointers"
- help
- If you say Y here the resulting kernel image will be slightly larger
- and slower, but it will give very useful debugging information.
- If you don't debug the kernel, you can say N, but we may not be able
- to solve problems without frame pointers.
-
endmenu
--
2.0.2
next prev parent reply other threads:[~2015-11-09 19:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-09 19:21 [PATCH 0/4] cleanup FRAME_POINTER kconfig option use Yang Shi
2015-11-09 19:21 ` Yang Shi [this message]
2015-11-09 19:21 ` [PATCH 2/4] hexagon: select ARCH_WANT_FRAME_POINTERS instead of defining FRAME_POINTER Yang Shi
2015-11-09 19:21 ` [PATCH 3/4] avr32: select ARCH_WANT_FRAME_POINTERS and set DEBUG_KERNEL in defconfigs Yang Shi
2015-11-10 6:43 ` Hans-Christian Noren Egtvedt
2015-11-09 19:21 ` [PATCH 4/4] h8300: " Yang Shi
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=1447096878-13519-2-git-send-email-yang.shi@linaro.org \
--to=yang.shi@linaro.org \
--cc=egtvedt@samfundet.no \
--cc=hskinnemoen@gmail.com \
--cc=linux-hexagon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rkuo@codeaurora.org \
--cc=uclinux-h8-devel@lists.sourceforge.jp \
--cc=ysato@users.sourceforge.jp \
/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®