On Sat, 7 Apr 2007 20:39:16 +0200 Sam Ravnborg <[EMAIL PROTECTED]> wrote:
> On Sat, Apr 07, 2007 at 10:59:47AM -0700, Andrew Morton wrote:
> > On Sat, 07 Apr 2007 10:20:17 -0700 Jeremy Fitzhardinge <[EMAIL PROTECTED]>
> > wrote:
> >
> > > I don't have a x86-64 compile environment on
> > >
On Sat, Apr 07, 2007 at 10:59:47AM -0700, Andrew Morton wrote:
> On Sat, 07 Apr 2007 10:20:17 -0700 Jeremy Fitzhardinge <[EMAIL PROTECTED]>
> wrote:
>
> > I don't have a x86-64 compile environment on
> > hand, so the 64 bits are completely untested
>
>
On Sat, 07 Apr 2007 10:20:17 -0700 Jeremy Fitzhardinge <[EMAIL PROTECTED]>
wrote:
> I don't have a x86-64 compile environment on
> hand, so the 64 bits are completely untested
http://userweb.kernel.org/~akpm/cross-compilers/
-
To unsubscribe from this list: send the line "unsubscribe
Andrew Morton wrote:
> x86_64 uses this too.
>
> WARNING: arch/x86_64/kernel/built-in.o - Section mismatch: reference to
> .init.text:mtrr_bp_init from .text.identify_cpu after 'identify_cpu' (at
> offset 0x655)
>
OK, two patches to follow: a x86-64 variant of the bugs.h cleanup, and a
On Fri, 06 Apr 2007 15:41:54 -0700 Jeremy Fitzhardinge <[EMAIL PROTECTED]>
wrote:
> identify_cpu() is used to identify both the boot CPU and secondary
> CPUs, but it performs some actions which only apply to the boot CPU.
> Those functions are therefore really __init functions, but because
>
On Fri, 06 Apr 2007 15:41:54 -0700 Jeremy Fitzhardinge [EMAIL PROTECTED]
wrote:
identify_cpu() is used to identify both the boot CPU and secondary
CPUs, but it performs some actions which only apply to the boot CPU.
Those functions are therefore really __init functions, but because
they're
Andrew Morton wrote:
x86_64 uses this too.
WARNING: arch/x86_64/kernel/built-in.o - Section mismatch: reference to
.init.text:mtrr_bp_init from .text.identify_cpu after 'identify_cpu' (at
offset 0x655)
OK, two patches to follow: a x86-64 variant of the bugs.h cleanup, and a
replacement
On Sat, 07 Apr 2007 10:20:17 -0700 Jeremy Fitzhardinge [EMAIL PROTECTED]
wrote:
I don't have a x86-64 compile environment on
hand, so the 64 bits are completely untested
http://userweb.kernel.org/~akpm/cross-compilers/
-
To unsubscribe from this list: send the line unsubscribe linux-kernel
On Sat, Apr 07, 2007 at 10:59:47AM -0700, Andrew Morton wrote:
On Sat, 07 Apr 2007 10:20:17 -0700 Jeremy Fitzhardinge [EMAIL PROTECTED]
wrote:
I don't have a x86-64 compile environment on
hand, so the 64 bits are completely untested
http://userweb.kernel.org/~akpm/cross-compilers/
On Sat, 7 Apr 2007 20:39:16 +0200 Sam Ravnborg [EMAIL PROTECTED] wrote:
On Sat, Apr 07, 2007 at 10:59:47AM -0700, Andrew Morton wrote:
On Sat, 07 Apr 2007 10:20:17 -0700 Jeremy Fitzhardinge [EMAIL PROTECTED]
wrote:
I don't have a x86-64 compile environment on
hand, so the 64 bits
identify_cpu() is used to identify both the boot CPU and secondary
CPUs, but it performs some actions which only apply to the boot CPU.
Those functions are therefore really __init functions, but because
they're called by identify_cpu(), they must be marked __cpuinit.
This patch splits
identify_cpu() is used to identify both the boot CPU and secondary
CPUs, but it performs some actions which only apply to the boot CPU.
Those functions are therefore really __init functions, but because
they're called by identify_cpu(), they must be marked __cpuinit.
This patch splits
12 matches
Mail list logo
