LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Cc: linux-kbuild <linux-kbuild@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [REVIEW for merge] kbuild updates including silence of section mismatch check
Date: Wed, 6 Feb 2008 21:58:23 +0100 [thread overview]
Message-ID: <20080206205823.GB12043@uranus.ravnborg.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0802051116410.1588@vixen.sonytel.be>
On Tue, Feb 05, 2008 at 11:38:49AM +0100, Geert Uytterhoeven wrote:
> On Sat, 2 Feb 2008, Sam Ravnborg wrote:
> > The most visible change is that I have made all the section mismatch
> > go away and in the end of the build modpost report the number
> > of section mismatch warnings and how to see detail.
> >
> > The typical output is now:
> >
> > modpost: Found 35 section mismatch(es).
> > To see full details build your kernel with:
> > 'make CONFIG_DEBUG_SECTION_MISMATCH=y'
>
> Can we get a `warning' string literal in that message, so I notice it when
> grepping for compiler warnings?
>
> ... Ah, there already exists a warn() routine, so let's use it.
>
> Subject: modpost: Use warn() for announcing section mismatches
Fair enough. Applied.
Sam
prev parent reply other threads:[~2008-02-06 20:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-02 20:35 Sam Ravnborg
2008-02-02 21:25 ` Frans Pop
2008-02-02 21:30 ` Sam Ravnborg
2008-02-03 3:30 ` Bryan Wu
2008-02-03 6:13 ` [PATCH try#2 ] kbuild: add svn revision information to setlocalversion Bryan Wu
2008-02-03 10:04 ` Sam Ravnborg
2008-02-02 22:37 ` [Additional PATCH] kbuild: do not warn about __*init/__*exit symbols being exported Sam Ravnborg
2008-02-05 10:38 ` [REVIEW for merge] kbuild updates including silence of section mismatch check Geert Uytterhoeven
2008-02-06 20:58 ` Sam Ravnborg [this message]
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=20080206205823.GB12043@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--subject='Re: [REVIEW for merge] kbuild updates including silence of section mismatch check' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).