From: rdunlap@xenotime.net (Randy Dunlap)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: reenable DEBUG_SECTION_MISMATCH
Date: Wed, 16 Feb 2011 09:29:02 -0800 [thread overview]
Message-ID: <20110216092902.3e6e97b2.rdunlap@xenotime.net> (raw)
In-Reply-To: <1297876993-4146-1-git-send-email-u.kleine-koenig@pengutronix.de>
On Wed, 16 Feb 2011 18:23:13 +0100 Uwe Kleine-K?nig wrote:
> For 2.6.38-rc4-git9 only 29 out of 133 defconfigs still produce section
> mismatches. These defconfigs produce 55 mismatches (weighted sum, so
> maybe less uniq mismatches).
>
> This is in my opinion enough to start scaring people about the remaining
> problems.
Yes, we have way too many of these and need more eyes on them.
> Signed-off-by: Uwe Kleine-K?nig <u.kleine-koenig@pengutronix.de>
> ---
> lib/Kconfig.debug | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
> index 3967c23..1130dd4 100644
> --- a/lib/Kconfig.debug
> +++ b/lib/Kconfig.debug
> @@ -102,7 +102,7 @@ config HEADERS_CHECK
>
> config DEBUG_SECTION_MISMATCH
> bool "Enable full Section mismatch analysis"
> - depends on UNDEFINED || (BLACKFIN)
> + depends on ARM || BLACKFIN
I would even like something like this:
depends on ARM || BLACKFIN || KERNEL_DEVELOPER
or even
select DEBUG_SECTION_MISMATCH if KERNEL_DEVELOPER
to make these warnings appear... but even with today's other warnings, lots
of them are ignored.
> default y
> # This option is on purpose disabled for now.
> # It will be enabled when we are down to a reasonable number
> --
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2011-02-16 17:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 17:23 [PATCH] ARM: reenable DEBUG_SECTION_MISMATCH Uwe Kleine-König
2011-02-16 17:29 ` Randy Dunlap [this message]
2011-02-16 19:33 ` Uwe Kleine-König
2011-02-16 20:07 ` Sam Ravnborg
2011-02-18 20:47 ` [PATCH] kbuild: reenable section mismatch analysis Uwe Kleine-König
2011-02-18 20:50 ` Randy Dunlap
2011-02-18 21:42 ` Mike Frysinger
2011-02-24 15:26 ` Michal Marek
2011-03-11 0:41 ` Andrew Morton
2011-03-11 0:44 ` Randy Dunlap
2011-03-11 1:00 ` Mike Frysinger
2011-03-11 1:05 ` Andrew Morton
2011-03-11 1:34 ` Mike Frysinger
2011-03-11 5:47 ` Sam Ravnborg
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=20110216092902.3e6e97b2.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=linux-arm-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).