From: Andrew Morton <akpm@osdl.org>
To: Christoph Lameter <clameter@sgi.com>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
linux-mm@kvack.org, Pekka Enberg <penberg@cs.helsinki.fi>,
Mel Gorman <mel@csn.ul.ie>
Subject: Re: mm section mismatches
Date: Mon, 9 Oct 2006 12:15:50 -0700 [thread overview]
Message-ID: <20061009121550.f251efff.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0610091104530.27654@schroedinger.engr.sgi.com>
On Mon, 9 Oct 2006 11:06:00 -0700 (PDT)
Christoph Lameter <clameter@sgi.com> wrote:
> On Sat, 7 Oct 2006, Randy Dunlap wrote:
>
> > > > > WARNING: vmlinux - Section mismatch: reference to .init.data:initkmem_list3 from .text between 'set_up_list3s' (at offset 0xc016ba8e) and 'kmem_flagcheck'
> > >
> > > This is non-init set_up_list3s() referring to __initdata initkmem_list3[]
> > > (Hi, Pekka and Christoph!)
> >
> > I can't repro that one either, so I'll let one of (...) fix it.
>
>
> set_up_list3s is only called during the bootstrap of the slab allocator.
> So this is fine.
Except it'll generate a scary warning for evermore.
It'd be nice to find some hack to make the warning go away, but I can't
think of one.
Maybe create a new section just for this purpose, put the function in that.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2006-10-09 19:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-07 1:49 mm section mismatches Andrew Morton
2006-10-07 4:10 ` Randy Dunlap
2006-10-07 6:46 ` Andrew Morton
2006-10-07 17:58 ` Randy Dunlap
2006-10-09 18:06 ` Christoph Lameter
2006-10-09 19:15 ` Andrew Morton [this message]
2006-10-09 14:38 ` Mel Gorman
2006-10-08 7:33 ` Pekka J Enberg
2006-10-08 21:51 ` Christoph Lameter
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=20061009121550.f251efff.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=clameter@sgi.com \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=penberg@cs.helsinki.fi \
--cc=rdunlap@xenotime.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.