From: Valdis.Kletnieks@vt.edu
To: Andi Kleen <andi@firstfloor.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: 2.6.26-rc* - CONFIG_FRAME_WARN help text clarification...
Date: Sat, 17 May 2008 09:28:12 -0400 [thread overview]
Message-ID: <74983.1211030892@turing-police.cc.vt.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1088 bytes --]
I hit this during a 'make oldconfig', and had to ponder and dig through the
Makefiles to see if pre-4.4 should set it to 0, or not.
Make it clear to people who hit this in a 'make oldconfig' that it's safe to
set it so that whenever their box finally *does* get gcc 4.4, it will be used.
Signed-Off-By: Valdis Kletnieks <valdis.kletnieks@vt.edu>
*** linux-2.6.26-rc2-mm1/lib/Kconfig.debug.gccvers 2008-05-17 09:14:05.000000000 -0400
--- linux-2.6.26-rc2-mm1/lib/Kconfig.debug 2008-05-17 09:15:45.000000000 -0400
***************
*** 34,40 ****
Tell gcc to warn at build time for stack frames larger than this.
Setting this too low will cause a lot of warnings.
Setting it to 0 disables the warning.
! Requires gcc 4.4
config MAGIC_SYSRQ
bool "Magic SysRq key"
--- 34,40 ----
Tell gcc to warn at build time for stack frames larger than this.
Setting this too low will cause a lot of warnings.
Setting it to 0 disables the warning.
! Requires gcc 4.4, but is safe to set for earlier releases.
config MAGIC_SYSRQ
bool "Magic SysRq key"
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next reply other threads:[~2008-05-17 13:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-17 13:28 Valdis.Kletnieks [this message]
2008-05-18 10:27 ` Andi Kleen
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=74983.1211030892@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®