From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from sj-iport-3.cisco.com ([171.71.176.72]:15043 "EHLO sj-iport-3.cisco.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755717AbYBARCI (ORCPT ); Fri, 1 Feb 2008 12:02:08 -0500 Subject: Re: Are Section mismatches out of control? References: <20080201104718.GA11717@uranus.ravnborg.org> <20080201030329.9b760777.akpm@linux-foundation.org> <1201864894.23523.117.camel@brick> From: Roland Dreier Date: Fri, 01 Feb 2008 09:02:00 -0800 In-Reply-To: <1201864894.23523.117.camel@brick> (Harvey Harrison's message of "Fri, 01 Feb 2008 03:21:34 -0800") Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-arch-owner@vger.kernel.org List-ID: To: Harvey Harrison Cc: Andrew Morton , Sam Ravnborg , LKML , linux arch , James Bottomley > 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.