From: Paul Mundt <lethal@linux-sh.org>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH] Kconfig.debug: combine Kconfig debug options
Date: Tue, 27 Jul 2004 15:02:11 -0400 [thread overview]
Message-ID: <20040727190210.GE20740@linux-sh.org> (raw)
In-Reply-To: <20040727104737.0de2da5b.rddunlap@osdl.org>
[-- Attachment #1: Type: text/plain, Size: 936 bytes --]
On Tue, Jul 27, 2004 at 10:47:37AM -0700, Randy.Dunlap wrote:
> DEBUG_SLAB is not available in cris, h8300, m68knommu, sh, sh64,
> or v850 AFAICT. Yes/no ?
>
This can be set for sh/sh64 just fine, it is pretty much generic anyways.
So placing this in a common Kconfig seems reasonable.
> | (didn't check the whole list) Perhaps the first instance of DEBUG_INFO
> | can depend on !SUPERH64 && !USERMODE only?
>
> It could. It depends on one's config (or code/patch) philosophy.
> I was trying to be explicit about which arches support a config option
> by including each arch in a list ("inclusion"). Or I could exclude
> certain arches from config options ("exclusion"). The inclusion
> method seems safer and more readable/maintainable to me, but that's
> just one opinion.
>
There's no need for the !SUPERH64 dependancy for DEBUG_INFO either, so
feel free to drop that if that's the way you end up going.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-07-27 19:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-24 6:11 [PATCH] Kconfig.debug: combine Kconfig debug options Randy.Dunlap
2004-07-27 12:55 ` Geert Uytterhoeven
2004-07-27 17:47 ` Randy.Dunlap
2004-07-27 19:02 ` Paul Mundt [this message]
2004-07-27 20:14 ` Randy.Dunlap
2004-07-27 21:29 ` Geert Uytterhoeven
2004-07-28 16:08 ` Randy.Dunlap
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=20040727190210.GE20740@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=akpm@osdl.org \
--cc=geert@linux-m68k.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox