From: "Randy.Dunlap" <rddunlap@osdl.org>
To: lkml <linux-kernel@vger.kernel.org>
Cc: akpm <akpm@osdl.org>
Subject: [PATCH] use Kconfig.debug (v2)
Date: Thu, 15 Apr 2004 22:03:38 -0700 [thread overview]
Message-ID: <20040415220338.3e351293.rddunlap@osdl.org> (raw)
Use generic lib/Kconfig.debug and arch-specific arch/*/Kconfig.debug.
Move KALLSYMS to generic debugging menu.
Changes from version 1:
1. remove global !CRIS && !H8300 from lib/Kconfig.debug;
2. for CRIS and H8300, don't source lib/Kconfig.debug (not used);
3. corrected several lib/Kconfig.debug ARCH usages;
4. small change in generic debug menu order (moved SPINLOCK
options together);
Ready for testing IMO. More comments?
Large patch (over 100 KB) to 2.6.6-rc1:
http://developer.osdl.org/rddunlap/patches/kconf_debug_266rc1.patch
arch/alpha/Kconfig | 103 ---------------------------
arch/alpha/Kconfig.debug | 54 ++++++++++++++
arch/arm/Kconfig | 159 -------------------------------------------
arch/arm/Kconfig.debug | 113 ++++++++++++++++++++++++++++++
arch/arm26/Kconfig | 112 ------------------------------
arch/arm26/Kconfig.debug | 58 +++++++++++++++
arch/cris/Kconfig | 13 ---
arch/cris/Kconfig.debug | 15 ++++
arch/h8300/Kconfig | 71 -------------------
arch/h8300/Kconfig.debug | 67 ++++++++++++++++++
arch/i386/Kconfig | 124 ---------------------------------
arch/i386/Kconfig.debug | 15 ++++
arch/ia64/Kconfig | 113 ------------------------------
arch/ia64/Kconfig.debug | 63 +++++++++++++++++
arch/m68k/Kconfig | 37 ----------
arch/m68k/Kconfig.debug | 9 ++
arch/m68knommu/Kconfig | 54 --------------
arch/m68knommu/Kconfig.debug | 42 +++++++++++
arch/mips/Kconfig | 110 -----------------------------
arch/mips/Kconfig.debug | 67 ++++++++++++++++++
arch/parisc/Kconfig | 48 ------------
arch/parisc/Kconfig.debug | 5 +
arch/ppc/Kconfig | 123 ---------------------------------
arch/ppc/Kconfig.debug | 72 +++++++++++++++++++
arch/ppc64/Kconfig | 79 ---------------------
arch/ppc64/Kconfig.debug | 27 +++++++
arch/s390/Kconfig | 55 --------------
arch/s390/Kconfig.debug | 5 +
arch/sh/Kconfig | 139 -------------------------------------
arch/sh/Kconfig.debug | 111 ++++++++++++++++++++++++++++++
arch/sparc/Kconfig | 71 -------------------
arch/sparc/Kconfig.debug | 13 +++
arch/sparc64/Kconfig | 98 --------------------------
arch/sparc64/Kconfig.debug | 38 ++++++++++
arch/um/Kconfig | 59 ---------------
arch/um/Kconfig.debug | 35 +++++++++
arch/v850/Kconfig | 28 -------
arch/v850/Kconfig.debug | 10 ++
arch/x86_64/Kconfig | 100 ---------------------------
arch/x86_64/Kconfig.debug | 47 ++++++++++++
init/Kconfig | 8 --
lib/Kconfig.debug | 147 +++++++++++++++++++++++++++++++++++++++
42 files changed, 1053 insertions(+), 1664 deletions(-)
Thanks,
--
~Randy
next reply other threads:[~2004-04-16 5:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-16 5:03 Randy.Dunlap [this message]
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 ` [PATCH] use Kconfig.debug (v3-proposed) (was: Re: [PATCH] use Kconfig.debug (v2)) Marc-Christian Petersen
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=20040415220338.3e351293.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®