From: Jacek Luczak <difrost.kernel@gmail.com>
To: Adrian Bunk <bunk@kernel.org>
Cc: sam@ravnborg.org, 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:22:10 +0200 [thread overview]
Message-ID: <480651E2.4060907@gmail.com> (raw)
In-Reply-To: <20080416175135.GN1677@cs181133002.pp.htv.fi>
Hi Adrian,
> 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'
> but CONFIG_DEBUG_SECTION_MISMATCH is not offered in 2.6.25.
Most of those ,,old mismatches'' where already fixed, so ...
> The options seem to be:
> - going back to the worse but for most practical purposes usable
> warnings in 2.6.24
> - don't show these warnings during modpost for 2.6.25
... IMO it would be better to not show modpost warnings. It will result in great
number of reports from users. Sam is here a boss.
There's also second part of the story around inline functions which may be
reported while running with CONFIG_DEBUG_SECTION_MISMATCH.
Greats,
Jacek
next prev parent reply other threads:[~2008-04-16 19:26 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 [this message]
2008-04-16 19:23 ` Sam Ravnborg
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=480651E2.4060907@gmail.com \
--to=difrost.kernel@gmail.com \
--cc=bunk@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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