public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Adrian Bunk <bunk@kernel.org>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6.25 and DEBUG_SECTION_MISMATCH
Date: Wed, 16 Apr 2008 21:23:06 +0200	[thread overview]
Message-ID: <20080416192306.GA3090@uranus.ravnborg.org> (raw)
In-Reply-To: <20080416175135.GN1677@cs181133002.pp.htv.fi>

Hi Adrian.

On Wed, Apr 16, 2008 at 08:51:35PM +0300, Adrian Bunk wrote:
> Hi Sam,
> 
> although DEBUG_SECTION_MISMATCH allows to also find exotig things like 
> finding bugs only present when using gcc < 3.4 and CONFIG_HOTPLUG=n at 
> the same time, the problem is that we print
>     WARNING: modpost: Found 13 section mismatch(es).
>     To see full details build your kernel with:
>     'make CONFIG_DEBUG_SECTION_MISMATCH=y'

So we print exact instructions how to get more info.
And several people has posted list of section mismatch warnings recently,
so the instructions are understood.
I fail to see any problem with that.

Obviously it would be better if we bailed out with a big fat warning
if someone _adds_ a new section mismatch warning.

> but CONFIG_DEBUG_SECTION_MISMATCH is not offered in 2.6.25.
If you by "not offered" try to say that the CONFIG option
is not available in kconfig then you are correct.
But you are in the instructions above asked to supply it
on the command line to make - not to enable it in the
kconfig configuration.

I would prefer we were down to less than 5 warnings so we could
enable it in kconfig but maybe after next merge window.

	Sam

  parent reply	other threads:[~2008-04-16 19:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-16 17:51 2.6.25 and DEBUG_SECTION_MISMATCH Adrian Bunk
2008-04-16 19:22 ` Jacek Luczak
2008-04-16 19:23 ` Sam Ravnborg [this message]
2008-04-16 19:31   ` Ingo Molnar
2008-04-16 19:49     ` Jacek Luczak
2008-04-16 19:55     ` Ingo Molnar
2008-04-16 20:52       ` Sam Ravnborg
2008-04-16 21:08         ` Ingo Molnar

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=20080416192306.GA3090@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=bunk@kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --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