From: Richard Holden <aciddeath@gmail•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: Tree for November 19 (section mismatche fpu_init)
Date: Wed, 19 Nov 2008 14:17:15 -0700 [thread overview]
Message-ID: <FF8068EB-1E4F-4D84-93B3-520922C5C1D4@gmail.com> (raw)
In-Reply-To: <20081119175917.7d21cf77.sfr@canb.auug.org.au>
WARNING: arch/x86/kernel/built-in.o(.cpuinit.text+0x1d6): Section
mismatch in reference from the function fpu_init() to the
function .init.text:init_thread_xstate()
The function __cpuinit fpu_init() references
a function __init init_thread_xstate().
If init_thread_xstate is only used by fpu_init then
annotate init_thread_xstate with a matching annotation.
appears in arch/x86/kernel/built-in.o
-Richard Holden
prev parent reply other threads:[~2008-11-19 21:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-19 6:59 linux-next: Tree for November 19 Stephen Rothwell
2008-11-19 18:48 ` linux-next: Tree for November 19 (staging/go7007/) Randy Dunlap
2008-11-19 19:08 ` Greg KH
2008-11-19 18:51 ` linux-next: Tree for November 19 (v4l2 warnings) Randy Dunlap
2008-11-20 0:02 ` Stephen Rothwell
2008-11-20 11:11 ` Mauro Carvalho Chehab
2008-11-19 18:53 ` linux-next: Tree for November 19 (mtd build error) Randy Dunlap
2008-11-19 18:58 ` David Woodhouse
2008-11-19 19:06 ` Randy Dunlap
2008-11-19 19:08 ` David Woodhouse
2008-11-19 19:18 ` Ben Hutchings
2008-11-19 19:24 ` David Woodhouse
2008-11-19 19:43 ` Ben Hutchings
2008-11-19 19:45 ` Randy Dunlap
2008-11-19 18:55 ` linux-next: Tree for November 19 (dvb build errors) Randy Dunlap
2008-11-19 18:59 ` linux-next: Tree for November 19 (ipw2100/2200 " Randy Dunlap
2008-11-19 19:15 ` [PATCH] coda: fix creds reference Randy Dunlap
2008-11-19 19:33 ` [PATCH -next resend] nfsctl: add headers for credentials Randy Dunlap
2008-11-19 21:17 ` Richard Holden [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=FF8068EB-1E4F-4D84-93B3-520922C5C1D4@gmail.com \
--to=aciddeath@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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