public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: linux-mtd@lists.infradead.org,
	lkml <linux-kernel@vger.kernel.org>,
	Adrian Hunter <adrian.hunter@nokia.com>
Subject: Re: [PATCH] ubifs: fix kconfig dependency warning
Date: Tue, 29 Mar 2011 10:02:58 +0300	[thread overview]
Message-ID: <1301382178.2816.69.camel@localhost> (raw)
In-Reply-To: <20110328134016.deb5d0c8.randy.dunlap@oracle.com>

On Mon, 2011-03-28 at 13:40 -0700, Randy Dunlap wrote:
> From: Randy Dunlap <randy.dunlap@oracle.com>
> 
> Fix another kconfig dependency warning, this time in ubifs.
> 
> warning: (UBIFS_FS_DEBUG && LOCKDEP && LATENCYTOP) selects KALLSYMS_ALL which has unmet direct dependencies (DEBUG_KERNEL && KALLSYMS)
> 
> Without this patch, we can have:
> # CONFIG_KALLSYMS is not set
> CONFIG_KALLSYMS_ALL=y
> which is useless (does nothing unless KALLSYMS is enabled).
> 
> However, ubifs builds successfully with or without this patch,
> and it builds with this line completely deleted,
> so what was this 'select' for?  Just developer convenience?

Well, here is the idea. You can compile UBIFS with debugging and without
debugging. Without debugging the resulting ubifs.ko is much smaller, so
some embedded people prefer it this way.

If you select debugging support, then we'll compile it a lot of
assertions, self-checks, test-modes, extra error messages with detailed
dumps. And we want to see stackdumps when errors or problems happen,
this is why we select KALLSYMS_ALL.

So I guess instead we should do:

select KALLSYMS
select KALLSYMS_ALL

?

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)

  reply	other threads:[~2011-03-29  7:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-28 20:40 [PATCH] ubifs: fix kconfig dependency warning Randy Dunlap
2011-03-29  7:02 ` Artem Bityutskiy [this message]
2011-03-29 15:01   ` Randy Dunlap
2011-03-29 15:04     ` Artem Bityutskiy
2011-03-29 15:48       ` [PATCH v2] " Randy Dunlap
2011-03-30  8:12         ` Artem Bityutskiy
2011-03-30 17:34           ` 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=1301382178.2816.69.camel@localhost \
    --to=dedekind1@gmail.com \
    --cc=adrian.hunter@nokia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=randy.dunlap@oracle.com \
    /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