From: Adrian Bunk <bunk@stusta.de>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] DEBUG_BUGVERBOSE for i386 (fwd)
Date: Wed, 17 Nov 2004 12:37:55 +0100 [thread overview]
Message-ID: <20041117113755.GL4943@stusta.de> (raw)
In-Reply-To: <20041117003032.7fd91c47.akpm@osdl.org>
On Wed, Nov 17, 2004 at 12:30:32AM -0800, Andrew Morton wrote:
> Adrian Bunk <bunk@stusta.de> wrote:
> >
> > The patch below implements CONFIG_DEBUG_BUGVERBOSE for i386 (more
> > exactly, it allows disabling the verbose BUG() reporting).
> >
> >
> > Signed-off-by: Adrian Bunk <bunk@fs.tum.de>
> >
> > --- linux-2.6.9-rc1-mm1-full/lib/Kconfig.debug.old 2004-08-29 21:22:20.000000000 +0200
> > +++ linux-2.6.9-rc1-mm1-full/lib/Kconfig.debug 2004-08-29 21:28:29.000000000 +0200
> > @@ -61,7 +61,7 @@
> >
> > config DEBUG_BUGVERBOSE
> > bool "Verbose BUG() reporting (adds 70K)"
> > - depends on DEBUG_KERNEL && (ARM || ARM26 || M68K || SPARC32 || SPARC64)
> > + depends on DEBUG_KERNEL && (ARM || ARM26 || M68K || SPARC32 || SPARC64 || (X86 && !X86_64))
>
> I think I'll stick an `&& EMBEDDED' in there to make it harder to disable
> BUG traces. We really don't want to be screwing ourselves over by removing
> useful diagnostic info.
I simply did it as on other architectures.
Do you want the following?
config DEBUG_BUGVERBOSE
bool "Verbose BUG() reporting (adds 70K)" if EMBEDDED
depends on (DEBUG_KERNEL || EMBEDDED=n) && (ARM || ...)
default y
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2004-11-17 11:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-17 4:32 [2.6 patch] DEBUG_BUGVERBOSE for i386 (fwd) Adrian Bunk
2004-11-17 8:30 ` Andrew Morton
2004-11-17 11:37 ` Adrian Bunk [this message]
2004-11-17 12:57 ` Roman Zippel
2004-11-17 13:08 ` Adrian Bunk
2004-11-17 13:25 ` Roman Zippel
2004-11-17 13:32 ` Adrian Bunk
2004-11-17 13:42 ` Roman Zippel
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=20041117113755.GL4943@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@osdl.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