From: Marc-Christian Petersen <m.c.p@kernel.linux-systeme.com>
To: linux-kernel@vger.kernel.org
Cc: "Randy.Dunlap" <rddunlap@osdl.org>, akpm@osdl.org
Subject: Re: [PATCH] use Kconfig.debug (v3-proposed) (was: Re: [PATCH] use Kconfig.debug (v2))
Date: Fri, 16 Apr 2004 23:38:14 +0200 [thread overview]
Message-ID: <200404162338.14345@WOLK> (raw)
In-Reply-To: <20040416110149.3e353333.rddunlap@osdl.org>
On Friday 16 April 2004 20:01, Randy.Dunlap wrote:
Hi Randy,
> Then let's move KALLSYMS to the very end of the menu.
> At the very least it should be after the last "depends on
> DEBUG_KERNEL" entry, but it still interferes with that
> dependency chain as either of us has it.
ok.
> Maybe do the same for parisc and s390, so that they don't show up
> at all?
dooh. Seems I forgot it :( - Sorry.
> sparc is the same way: only entry(s) depend on DEBUG_KERNEL.
> Same for x86_64.
yes.
> However, I did it that way for "future-proofing". Makes it
> easy for someone to add an entry without having to think about
> higher-level parameters/values etc.
good point, but for now it may confuse people. Once someone's gonna put
selectable stuff in there we can change that back at once :)
ciao, Marc
prev parent reply other threads:[~2004-04-16 21:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-16 5:03 [PATCH] use Kconfig.debug (v2) Randy.Dunlap
2004-04-16 8:42 ` [PATCH] use Kconfig.debug (v3-proposed) (was: Re: [PATCH] use Kconfig.debug (v2)) Marc-Christian Petersen
2004-04-16 18:01 ` Randy.Dunlap
2004-04-16 21:22 ` Randy.Dunlap
2004-04-16 21:43 ` Marc-Christian Petersen
2004-04-16 23:04 ` [PATCH] use Kconfig.debug (v4) Randy.Dunlap
2004-04-16 21:38 ` Marc-Christian Petersen [this message]
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=200404162338.14345@WOLK \
--to=m.c.p@kernel.linux-systeme.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.