From: Adrian Bunk <bunk@stusta.de>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] DEBUG_BUGVERBOSE for i386 (fwd)
Date: Wed, 17 Nov 2004 14:08:20 +0100 [thread overview]
Message-ID: <20041117130820.GQ4943@stusta.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0411171347300.17266@scrub.home>
On Wed, Nov 17, 2004 at 01:57:05PM +0100, Roman Zippel wrote:
> Hi,
Hi Roman,
> On Wed, 17 Nov 2004, Adrian Bunk wrote:
>
> > 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
>
> What are you trying to do here?
- if EMBEDDED=n, always enable it
- if EMBEDDED=y:
- disable if DEBUG_KERNEL=n
- ask if DEBUG_KERNEL=y
> I guess you want something more like this?
>
> config DEBUG_BUGVERBOSE
> bool "Verbose BUG() reporting (adds 70K)" if DEBUG_KERNEL && EMBEDDED
> depends on ARM || ...
> default y
This has a different semantics:
If you want no kernel debugging in an embedded environment,
DEBUG_BUGVERBOSE would be automatically enabled.
This is definitely not intended.
> bye, Roman
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 13:10 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
2004-11-17 12:57 ` Roman Zippel
2004-11-17 13:08 ` Adrian Bunk [this message]
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=20041117130820.GQ4943@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zippel@linux-m68k.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