[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1252151177.4969.11.camel@ht.satnam>
Date: Sat, 05 Sep 2009 17:16:17 +0530
From: Jaswinder Singh Rajput <jaswinder@...nel.org>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: x86 maintainers <x86@...nel.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86: Fix 20 section mismatch warnings from x86_init,
arch/x86/kernel/x86_init.c
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@...il.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists