From: Jaswinder Singh Rajput <jaswinder@kernel.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: x86 maintainers <x86@kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: Fix 20 section mismatch warnings from x86_init, arch/x86/kernel/x86_init.c
Date: Sat, 19 Sep 2009 10:13:13 +0530 [thread overview]
Message-ID: <1253335393.3309.7.camel@ht.satnam> (raw)
In-Reply-To: <1252151177.4969.11.camel@ht.satnam>
[RESENDING]
On Sat, 2009-09-05 at 17:16 +0530, Jaswinder Singh Rajput wrote:
> On Sat, 2009-09-05 at 16:50 +0530, Jaswinder Singh Rajput wrote:
> > Check http://marc.info/?l=linux-kernel&m=125214951924366&w=2 to see more details.
> >
> > Signed-off-by: Jaswinder Singh Rajput <jaswinderrajput@gmail.com>
> > ---
> > arch/x86/kernel/x86_init.c | 2 +-
> > 1 files changed, 1 insertions(+), 1 deletions(-)
> >
> > diff --git a/arch/x86/kernel/x86_init.c b/arch/x86/kernel/x86_init.c
> > index 24be7f3..81dd9d0 100644
> > --- a/arch/x86/kernel/x86_init.c
> > +++ b/arch/x86/kernel/x86_init.c
> > @@ -23,7 +23,7 @@ void __init x86_init_pgd_noop(pgd_t *unused) { }
> > * The platform setup functions are preset with the default functions
> > * for standard PC hardware.
> > */
> > -struct __initdata x86_init_ops x86_init = {
> > +struct __initdata x86_init_ops x86_init_ops = {
> >
> > .resources = {
> > .probe_roms = x86_init_noop,
>
> x86_init is used by many files and this breaks the kernel :
>
> arch/x86/built-in.o: In function `init_IRQ':
> (.text+0x4b12): undefined reference to `x86_init'
> arch/x86/built-in.o: In function `trap_init':
> (.init.text+0x385): undefined reference to `x86_init'
> arch/x86/built-in.o: In function `x86_late_time_init':
> time.c:(.init.text+0x39f): undefined reference to `x86_init'
> arch/x86/built-in.o: In function `setup_arch':
> (.init.text+0x80b): undefined reference to `x86_init'
> arch/x86/built-in.o: In function `setup_arch':
> (.init.text+0xa32): undefined reference to `x86_init'
> arch/x86/built-in.o:(.init.text+0xc5e): more undefined references to `x86_init' follow
>
> Now we need to look for some another option.
>
> Thomas, any suggestions.
>
> Thank you,
> --
> JSR
prev parent reply other threads:[~2009-09-19 4:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-05 11:14 20 Section mismatch warnings from x86_init, arch/x86/kernel/x86_init.c Jaswinder Singh Rajput
2009-09-05 11:20 ` [PATCH] x86: Fix 20 section " Jaswinder Singh Rajput
2009-09-05 11:46 ` Jaswinder Singh Rajput
2009-09-19 4:43 ` Jaswinder Singh Rajput [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=1253335393.3309.7.camel@ht.satnam \
--to=jaswinder@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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