public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Michal Marek <mmarek@suse.cz>,
	bp@alien8.de, dot@dotat.at, mikew@google.com,
	randy.dunlap@oracle.com, linux-kbuild@vger.kernel.org,
	linux-kernel@vger.kernel.org, Mike Frysinger <vapier@gentoo.org>,
	Randy Dunlap <rdunlap@xenotime.net>
Subject: Re: [GIT] kbuild core updates for 2.6.39-rc1
Date: Mon, 21 Mar 2011 08:47:48 +0100	[thread overview]
Message-ID: <20110321074748.GF27124@pengutronix.de> (raw)
In-Reply-To: <AANLkTin5vYaU83K0YOdD1OgCS24LA8XBSvNfmGFnjhGF@mail.gmail.com>

On Sun, Mar 20, 2011 at 05:53:24PM -0700, Linus Torvalds wrote:
> On Sat, Mar 19, 2011 at 1:58 AM, Michal Marek <mmarek@suse.cz> wrote:
> >
> > * Section mismatch analysis enabled by default
> >  - there are only a few warnings for defconfig builds,
> >    all{yes,mod}config still has a lot of them. Depending on the general
> >    perception of this change, we might disable it later in the rc phase
> >    again.
> 
> No.
> 
> We don't enable stuff like this by default. Not when it actually
> changes some really fundamental compiler flags, and thus the whole "we
> can disable it late in -rc again" is a totally broken option, since if
> we have any compiler issues, we'd want to know it early.
Note that the default y doesn't result from the patch in this pull
request but from 
	1d53661 (blackfin: enable DEBUG_SECTION_MISMATCH)
. I admit I didn't think deeply about it, but keeping it seemed OK for
me.

> And we _know_ we are going to disable it, since it enables the "don't
> inline" flag to gcc for called-once functions. So there's no question
> at all what the default should be in any release kernel.
I wasn't aware of that, Mike so even "default y if BLACKFIN" seems to be
a bad idea.

Michal, do you want just remove the default y and squash it into the
commit?
And something that just occured my now is that the warning about
CONFIG_DEBUG_SECTION_MISMATCH in scripts/mod/modpost.c could get an
update, too.  Something like:

 		warn("modpost: Found %d section mismatch(es).\n"
-		     "To see full details build your kernel with:\n"
-		     "'make CONFIG_DEBUG_SECTION_MISMATCH=y'\n",
+		     "To see full details enable CONFIG_DEBUG_SECTION_MISMATCH in your .config.\n"
		     sec_mismatch_count);

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

  reply	other threads:[~2011-03-21  7:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-19  8:58 [GIT] kbuild core updates for 2.6.39-rc1 Michal Marek
2011-03-21  0:53 ` Linus Torvalds
2011-03-21  7:47   ` Uwe Kleine-König [this message]
2011-03-21 10:17     ` Michal Marek

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=20110321074748.GF27124@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=bp@alien8.de \
    --cc=dot@dotat.at \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikew@google.com \
    --cc=mmarek@suse.cz \
    --cc=randy.dunlap@oracle.com \
    --cc=rdunlap@xenotime.net \
    --cc=torvalds@linux-foundation.org \
    --cc=vapier@gentoo.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