[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070205170501.GA6537@elte.hu>
Date: Mon, 5 Feb 2007 18:05:01 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: David Woodhouse <dwmw2@...radead.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [patch] MTD: fix DOC2000/2001/2001PLUS build error
* Linus Torvalds <torvalds@...ux-foundation.org> wrote:
> Me, I'd like to say I want "default firewall built in", and not have
> to see *any* of the crap. And that's exactly why "select" is a good
> thing.
yeah. For a long time i wanted to do something like that for all the
kernel debugging options, to by default only offer a simple menu of:
( ) Debug Disabled
(*) Transparent Low-Overhead Debugging
( ) Transparent Medium-Overhead Debugging
( ) Transparent High-Overhead Debugging
( ) Custom Debugging
so say softlockup-detect or spinlock-sleep checks would be enabled by
Low-Overhead Debugging, but slab-debug or lockdep would only be enabled
by the High-Overhead Debugging option.
and all the zillions of debug options would only show up if "Custom
Debugging" is selected. Plus this would have the advantage that if we
add a new debug option, and the tester already has a .config with say
"Transparent Low-Overhead Debugging" enabled - Kconfig would pick the
right value for that new debug option. This would remove the need and
desire to 'default y' certain debugging features to get them tested ...
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists