From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from fk-out-0910.google.com ([209.85.128.184]:53744 "EHLO fk-out-0910.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750822AbYDPT0B (ORCPT ); Wed, 16 Apr 2008 15:26:01 -0400 Received: by fk-out-0910.google.com with SMTP id 19so2933281fkr.5 for ; Wed, 16 Apr 2008 12:25:59 -0700 (PDT) Message-ID: <480651E2.4060907@gmail.com> Date: Wed, 16 Apr 2008 21:22:10 +0200 From: Jacek Luczak MIME-Version: 1.0 Subject: Re: 2.6.25 and DEBUG_SECTION_MISMATCH References: <20080416175135.GN1677@cs181133002.pp.htv.fi> In-Reply-To: <20080416175135.GN1677@cs181133002.pp.htv.fi> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kbuild-owner@vger.kernel.org List-ID: To: Adrian Bunk Cc: sam@ravnborg.org, linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org 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