From: linas@austin.ibm.com (Linas Vepstas)
To: Gabriel Paubert <paubert@iram.es>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Andrew Morton <akpm@linux-foundation.org>,
paulus@samba.org, LKML <linux-kernel@vger.kernel.org>,
ppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: Section mismatch warnings (was Re: [PATCH] early_pfn_to_nid needs to be __meminit)
Date: Wed, 9 May 2007 14:45:03 -0500 [thread overview]
Message-ID: <20070509194503.GZ4452@austin.ibm.com> (raw)
In-Reply-To: <20070509165115.GA23576@iram.es>
On Wed, May 09, 2007 at 06:51:15PM +0200, Gabriel Paubert wrote:
> On Thu, May 10, 2007 at 02:25:52AM +1000, Stephen Rothwell wrote:
> > This removes a section mismatch warning in those circumstances.
>
> Speaking of this, I just tried to compile an official (Linus' git tree)
> kernel for my old PMac G4 and I get a lot of section mismatch warnings at
> the end of the compilation:
>
> WARNING: arch/powerpc/mm/built-in.o - Section mismatch: reference to .init.text:early_get_page from .text between 'pte_alloc_one_kernel' (at offset 0xf50) and 'v_mapped_by_bats'
>
> I find these 50 or so warnings so scary that I've not yet tried
> to boot the kernel. Note that this is a non-modular kernel.
I'm getting oodles of these on an older -mm2 tree. The kernels seem to
work fine. Yes, they should be fixed but I'm up to my proverbial eyballs
in alligators.
--linas
next prev parent reply other threads:[~2007-05-09 19:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-09 16:25 [PATCH] early_pfn_to_nid needs to be __meminit Stephen Rothwell
2007-05-09 16:51 ` Section mismatch warnings (was Re: [PATCH] early_pfn_to_nid needs to be __meminit) Gabriel Paubert
2007-05-09 19:45 ` Linas Vepstas [this message]
2007-05-09 19:58 ` Josh Boyer
2007-05-10 5:41 ` Yasunori Goto
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=20070509194503.GZ4452@austin.ibm.com \
--to=linas@austin.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paubert@iram.es \
--cc=paulus@samba.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).