From: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: trini@kernel.crashing.org, linux-kernel@vger.kernel.org,
akpm@osdl.org, jgarzik@pobox.com, mpm@selenic.com,
zwane@linuxpower.ca
Subject: Re: [PATCH] Kconfig.debug family
Date: Thu, 29 Apr 2004 20:54:49 +0200 [thread overview]
Message-ID: <200404292054.49663.bzolnier@elka.pw.edu.pl> (raw)
In-Reply-To: <20040429095143.6de85098.rddunlap@osdl.org>
On Thursday 29 of April 2004 18:51, Randy.Dunlap wrote:
> On Thu, 29 Apr 2004 18:42:23 +0200 Bartlomiej Zolnierkiewicz wrote:
> | Only on x86 it does a proper thing:
> |
> | arch/<arch>/Kconfig -> arch/<arch>/Kconfig.debug -> lib/Kconfig.debug
>
> That's because I goofed up... it's the wrong patch.
>
> I was trying something that someone suggested (You!) and it didn't
:)
> work out in a desirable way as far as how it's presented in
> {x,menu}config, so I need to fix that (i386 part) and then you
In your previous patch (vs 2.6.5) there was only one "Kernel hacking" menu,
in this one there are two menus: "Kernel hacking" and "X86 kernel hacking".
I hacked it quickly and I have one menu again (on x86 arch specific options
are not configurable) so I also hacked+checked ppc and 'make menuconfig'
looks OK). Did I miss something?
diff -u linux-2.6.6-rc2-bk4-bzolnier/arch/i386/Kconfig.debug linux-2.6.6-rc2-bk4-bzolnier/arch/i386/Kconfig.debug
--- linux-2.6.6-rc2-bk4-bzolnier/arch/i386/Kconfig.debug 2004-04-29 20:31:57.358189632 +0200
+++ linux-2.6.6-rc2-bk4-bzolnier/arch/i386/Kconfig.debug 2004-04-29 20:45:11.884403288 +0200
@@ -1,6 +1,7 @@
-source "lib/Kconfig.debug"
-menu "X86 kernel hacking"
+menu "Kernel hacking"
+
+source "lib/Kconfig.debug"
config X86_FIND_SMP_CONFIG
bool
diff -u linux-2.6.6-rc2-bk4-bzolnier/arch/ppc/Kconfig linux-2.6.6-rc2-bk4-bzolnier/arch/ppc/Kconfig
--- linux-2.6.6-rc2-bk4-bzolnier/arch/ppc/Kconfig 2004-04-29 20:31:57.396183856 +0200
+++ linux-2.6.6-rc2-bk4-bzolnier/arch/ppc/Kconfig 2004-04-29 20:45:49.703653888 +0200
@@ -1108,7 +1108,7 @@
source "lib/Kconfig"
-source "lib/Kconfig.debug"
+source "arch/ppc/Kconfig.debug"
source "security/Kconfig"
diff -u linux-2.6.6-rc2-bk4-bzolnier/arch/ppc/Kconfig.debug linux-2.6.6-rc2-bk4-bzolnier/arch/ppc/Kconfig.debug
--- linux-2.6.6-rc2-bk4-bzolnier/arch/ppc/Kconfig.debug 2004-04-29 20:31:57.397183704 +0200
+++ linux-2.6.6-rc2-bk4-bzolnier/arch/ppc/Kconfig.debug 2004-04-29 20:45:33.027189096 +0200
@@ -1,4 +1,6 @@
-menu "PPC kernel hacking"
+menu "Kernel hacking"
+
+source "lib/Kconfig.debug"
config KGDB
bool "Include kgdb kernel debugger"
@@ -66 +67,0 @@
-
diff -u linux-2.6.6-rc2-bk4-bzolnier/lib/Kconfig.debug linux-2.6.6-rc2-bk4-bzolnier/lib/Kconfig.debug
--- linux-2.6.6-rc2-bk4-bzolnier/lib/Kconfig.debug 2004-04-29 20:31:57.439177320 +0200
+++ linux-2.6.6-rc2-bk4-bzolnier/lib/Kconfig.debug 2004-04-29 20:39:43.907263392 +0200
@@ -1,6 +1,4 @@
-# Generic debug menu
-
-menu "Kernel hacking"
+# Generic debug options
config DEBUG_KERNEL
bool "Kernel debugging"
@@ -97,7 +95,7 @@
debugging info resulting in a larger kernel image.
Say Y here only if you plan to use gdb to debug the kernel.
If you don't debug the kernel, you can say N.
-
+
config FRAME_POINTER
bool "Compile the kernel with frame pointers"
depends on DEBUG_KERNEL && (!ARM && !ARM26 && !X86_64 && !S390 && !V850 && !SPARC64)
@@ -148,3 +145,0 @@
-
-endmenu
-
> can complain some more. :)
:)
Bartlomiej
next prev parent reply other threads:[~2004-04-29 18:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-22 3:51 Randy.Dunlap
2004-04-22 3:59 ` Zwane Mwaikambo
2004-04-22 4:07 ` Andrew Morton
2004-04-26 16:42 ` Tom Rini
2004-04-29 15:38 ` Randy.Dunlap
2004-04-29 15:50 ` Tom Rini
2004-04-29 16:42 ` Bartlomiej Zolnierkiewicz
2004-04-29 16:51 ` Randy.Dunlap
2004-04-29 18:54 ` Bartlomiej Zolnierkiewicz [this message]
2004-04-29 19:46 ` Randy.Dunlap
2004-04-29 20:52 ` [PATCH] Kconfig.debug family (v3-bart) Randy.Dunlap
-- strict thread matches above, loose matches on Subject: below --
2004-04-21 3:47 [PATCH] Kconfig.debug family 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=200404292054.49663.bzolnier@elka.pw.edu.pl \
--to=b.zolnierkiewicz@elka.pw.edu.pl \
--cc=akpm@osdl.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=rddunlap@osdl.org \
--cc=trini@kernel.crashing.org \
--cc=zwane@linuxpower.ca \
/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®