On Wed, Jul 8, 2015 at 11:51 AM, Yannick GICQUEL
<[email protected]> wrote:
> diff --git a/arch/m68k/kernel/setup_mm.c b/arch/m68k/kernel/setup_mm.c
> index 5b8ec4d..0bc6f77 100644
> --- a/arch/m68k/kernel/setup_mm.c
> +++ b/arch/m68k/kernel/setup_mm.c
> @@ -245,7 +245,7 @@ void __init setup_arch(char **cmdline_p)
> * We should really do our own FPU check at startup.
> * [what do we do with buggy 68LC040s? if we have problems
> * with them, we should add a test to check_bugs() below] */
> -#ifndef CONFIG_M68KFPU_EMU_ONLY
> +#if !defined(CONFIG_M68KFPU_EMU_ONLY) && defined(CONFIG_FPU)
> /* clear the fpu if we have one */
> if (m68k_fputype &
> (FPU_68881|FPU_68882|FPU_68040|FPU_68060|FPU_COLDFIRE)) {
> volatile int zero = 0;
Should we turn M68KFPU_EMU_ONLY into !FPU in general?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
