public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: starvik@axis.com
To: Adrian Bunk <bunk@stusta.de>
Cc: Andrew Morton <akpm@osdl.org>,
	dev-etrax@axis.com, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] arch/cris/Kconfig.debug: use lib/Kconfig.debug
Date: Mon,  8 Aug 2005 14:36:08 +0200	[thread overview]
Message-ID: <1123504568.42f751b890ba2@webmail-unix.se.axis.com> (raw)
In-Reply-To: <20050807220005.GC4006@stusta.de>

Acked-by: Mikael Starvik <starvik@axis.com>

> This patch converts arch/cris/Kconfig.debug to using lib/Kconfig.debug.
> 
> This should fix a compile error in 2.6.13-rc4 caused by a missing 
> CONFIG_LOG_BUF_SHIFT definition.
> 
> While I was editing this file, I also converted some spaces to tabs.
> 
> 
> Signed-off-by: Adrian Bunk <bunk@stusta.de>
> 
> ---
> 
> This patch was already sent on:
> - 31 Jul 2005
> 
>  arch/cris/Kconfig.debug |   31 ++++++++++---------------------
>  1 files changed, 10 insertions(+), 21 deletions(-)
> 
> --- linux-2.6.13-rc4-mm1/arch/cris/Kconfig.debug.old	2005-07-31
> 18:29:15.000000000 +0200
> +++ linux-2.6.13-rc4-mm1/arch/cris/Kconfig.debug	2005-07-31
> 18:32:15.000000000 +0200
> @@ -5,10 +5,13 @@
>  	bool "Kernel profiling support"
>  
>  config SYSTEM_PROFILER
> -        bool "System profiling support"
> +	bool "System profiling support"
> +
> +source "lib/Kconfig.debug"
>  
>  config ETRAX_KGDB
>  	bool "Use kernel GDB debugger"
> +	depends on DEBUG_KERNEL
>  	---help---
>  	  The CRIS version of gdb can be used to remotely debug a running
>  	  Linux kernel via the serial debug port.  Provided you have gdb-cris
> @@ -22,25 +25,11 @@
>  	  this option is turned on!
>  
>  
> -config DEBUG_INFO
> -        bool "Compile the kernel with debug info"
> -        help
> -          If you say Y here the resulting kernel image will include
> -          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"
> -        help
> -          If you say Y here the resulting kernel image will be slightly
> larger
> -          and slower, but it will give very useful debugging information.
> -          If you don't debug the kernel, you can say N, but we may not be
> able
> -          to solve problems without frame pointers.
> -
>  config DEBUG_NMI_OOPS
> -       bool "NMI causes oops printout"
> -       help
> -         If the system locks up without any debug information you can say Y
> -         here to make it possible to dump an OOPS with an external NMI.
> +	bool "NMI causes oops printout"
> +	depends on DEBUG_KERNEL
> +	help
> +	  If the system locks up without any debug information you can say Y
> +	  here to make it possible to dump an OOPS with an external NMI.
> +
>  endmenu
> 




-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/

  reply	other threads:[~2005-08-08 12:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-07 22:00 [2.6 patch] arch/cris/Kconfig.debug: use lib/Kconfig.debug Adrian Bunk
2005-08-08 12:36 ` starvik [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-07-31 16:39 Adrian Bunk

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=1123504568.42f751b890ba2@webmail-unix.se.axis.com \
    --to=starvik@axis.com \
    --cc=akpm@osdl.org \
    --cc=bunk@stusta.de \
    --cc=dev-etrax@axis.com \
    --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