All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@in.ibm.com>
To: kexec@lists.infradead.org
Subject: Re: DEBUG_INFO -> DEBUG_KERNEL dependency
Date: Thu, 6 Sep 2007 11:18:58 +0530	[thread overview]
Message-ID: <20070906054858.GD17336@in.ibm.com> (raw)
In-Reply-To: <20070905122311.GA11013@suse.de>

On Wed, Sep 05, 2007 at 02:23:11PM +0200, Bernhard Walle wrote:
> Hi,
> 
> Subject says all. Why does DEBUG_INFO depend on DEBUG_KERNEL? IMO it's
> also desirable to use Kdump when DEBUG_KERNEL is not enabled.
> 

That's true. But is DEBUG_KERNEL hurting you. You can disable all other
debug options under DEBUG_KERNEL and only enable DEBUG_INFO.

Logically it makes sense to put all kernel debug features under KERNEL_DEBUG.
Though DEBUG_INFO probably can be brought out. But is there huge piece
of code under DEBUG_KERNEL which is a problem for you?

Thanks
Vivek

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

      reply	other threads:[~2007-09-06  5:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-05 12:23 DEBUG_INFO -> DEBUG_KERNEL dependency Bernhard Walle
2007-09-06  5:48 ` Vivek Goyal [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=20070906054858.GD17336@in.ibm.com \
    --to=vgoyal@in.ibm.com \
    --cc=kexec@lists.infradead.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.