From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Marc-Christian Petersen <m.c.p@kernel.linux-systeme.com>
Cc: linux-kernel@vger.kernel.org, mpm@selenic.com, jgarzik@pobox.com,
akpm@osdl.org
Subject: Re: PATCH] Kconfig.debug family
Date: Thu, 15 Apr 2004 14:41:26 -0700 [thread overview]
Message-ID: <20040415144126.702d3480.rddunlap@osdl.org> (raw)
In-Reply-To: <200404152336.30621@WOLK>
On Thu, 15 Apr 2004 23:36:30 +0200 Marc-Christian Petersen wrote:
| On Thursday 15 April 2004 22:52, Randy.Dunlap wrote:
|
| Hi Randy,
|
| > This patch:
| > - creates lib/Kconfig.debug for generic kernel debug options
| > - creates arch/*/Kconfig.debug for arch-specific debug options
| > - moves KALLSYMS to the generic kernel debug options list
| > This is a first cut for review/comments. I will double-check
| > the generic options list to see how it needs to be corrected...
|
| I really appreciate it. But I have one comment/suggestion:
|
| We might use lib/Kconfig.debug for all arches and use proper "depend on" if
| there is stuff for some specific arch only. So we have every debug stuff just
| in one file. What do you think?
Hi Marc,
That sounds like my first version (unposted), which failed IMO.
It looks OK if you/user does not enable viewing all flags/options
(in [xg]config -- I used xconfig). However, if those options are
enabled, you/user sees all config options for all architectures,
and I didn't find that acceptable. Feel free to disagree with me
and persuade me otherwise, because having them *all* in
lib/Kconfig.debug is nicer IMO.
The full patch to do this (against 2.6.5-bk2) is now available at:
http://developer.osdl.org/rddunlap/patches/kconfig_debug_265bk2.patch
if you or anyone else wants to compare how they look.
Thanks,
--
~Randy
next prev parent reply other threads:[~2004-04-15 21:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-14 7:43 [PATCH] conditionalize some boring buffer_head checks Jeff Garzik
2004-04-14 7:58 ` Andrew Morton
2004-04-14 8:02 ` Andrew Morton
2004-04-14 8:10 ` Jeff Garzik
2004-04-14 8:16 ` Andrew Morton
2004-04-14 8:45 ` Jeff Garzik
2004-04-14 9:10 ` Jeff Garzik
2004-04-14 21:25 ` Matt Mackall
2004-04-14 21:27 ` Randy.Dunlap
2004-04-14 21:37 ` Matt Mackall
2004-04-14 21:33 ` Jeff Garzik
2004-04-14 21:49 ` Matt Mackall
2004-04-15 6:12 ` Zwane Mwaikambo
2004-04-15 20:52 ` PATCH] Kconfig.debug family Randy.Dunlap
2004-04-15 21:36 ` Sam Ravnborg
2004-04-15 21:36 ` Marc-Christian Petersen
2004-04-15 21:41 ` Randy.Dunlap [this message]
2004-04-14 8:27 ` [PATCH] conditionalize some boring buffer_head checks Tim Hockin
2004-04-14 8:48 ` Jeff Garzik
2004-04-14 13:31 ` Chris Friesen
2004-04-14 15:05 ` Randy.Dunlap
2004-04-14 8:29 ` Jens Axboe
2004-04-14 8:42 ` Jeff Garzik
2004-04-14 8:47 ` Jens Axboe
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=20040415144126.702d3480.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=akpm@osdl.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.c.p@kernel.linux-systeme.com \
--cc=mpm@selenic.com \
/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®