From: Roland Dreier <rdreier@cisco.com>
To: Harvey Harrison <harvey.harrison@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Sam Ravnborg <sam@ravnborg.org>,
LKML <linux-kernel@vger.kernel.org>,
linux arch <linux-arch@vger.kernel.org>,
James Bottomley <James.Bottomley@HansenPartnership.com>
Subject: Re: Are Section mismatches out of control?
Date: Fri, 01 Feb 2008 09:02:00 -0800 [thread overview]
Message-ID: <adak5lo7gqf.fsf@cisco.com> (raw)
In-Reply-To: <1201864894.23523.117.camel@brick> (Harvey Harrison's message of "Fri, 01 Feb 2008 03:21:34 -0800")
> Subject to someone _making_ it an issue, can't see it changing.
Actually I think that Sam's recent improvements to the section
mismatch detection should make it easy to get at least all of the
driver issues fixed -- the problem in the past was that many warnings
would only show with certain configs or certain compilers (inlining
functions only called once would hide many warnings).
Now I just need to enable CONFIG_DEBUG_SECTION_MISMATCH and I'm pretty
certain to see everything (and indeed this found a few warnings in
drivers/infiniband hidden by inlining, which I've queued up a fix for).
So the __cpuinit stuff may be trickier and half false positives etc,
but I'm confident drivers/ will be cleaned up quickly now thanks to Sam.
next prev parent reply other threads:[~2008-02-01 17:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-01 10:47 Are Section mismatches out of control? Sam Ravnborg
2008-02-01 11:03 ` Andrew Morton
2008-02-01 11:21 ` Harvey Harrison
2008-02-01 13:30 ` Geert Uytterhoeven
2008-02-01 13:40 ` Sam Ravnborg
2008-02-01 21:22 ` Geert Uytterhoeven
2008-02-01 22:32 ` Sam Ravnborg
2008-02-02 16:42 ` Geert Uytterhoeven
2008-02-02 17:40 ` Sam Ravnborg
2008-02-01 17:02 ` Roland Dreier [this message]
2008-02-01 21:47 ` Jan Engelhardt
2008-02-01 22:10 ` James Bottomley
2008-02-01 22:40 ` Sam Ravnborg
2008-02-02 0:01 ` Jan Engelhardt
2008-02-01 14:48 ` Johannes Weiner
2008-02-01 15:00 ` James Bottomley
2008-02-01 16:43 ` Jeff Garzik
2008-02-01 20:17 ` Sam Ravnborg
2008-02-01 20:24 ` Jeff Garzik
2008-02-01 22:38 ` Sam Ravnborg
2008-02-01 11:10 ` Andi Kleen
2008-02-01 21:51 ` Jan Engelhardt
2008-02-02 4:12 ` Andi Kleen
2008-02-01 14:53 ` James Bottomley
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=adak5lo7gqf.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=harvey.harrison@gmail.com \
--cc=linux-arch@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