O> a non-identical CPU system with a geode + something else doesn't exist > and is very unlikely to happen. As the Geode isn't used SMP (and afaik isnt SMP capable) that would be a reasonable assumption - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- References:
- [PATCH]gx-suspmod.c use boot_cpu_data instead of current_cpu_data
- From: Dave Young <hidave.darkstar@gmail.com>
- Re: [PATCH]gx-suspmod.c use boot_cpu_data instead of current_cpu_data
- From: Andrew Morton <akpm@linux-foundation.org>
- Re: [PATCH]gx-suspmod.c use boot_cpu_data instead of current_cpu_data
- From: "Dave Young" <hidave.darkstar@gmail.com>
- Re: [PATCH]gx-suspmod.c use boot_cpu_data instead of current_cpu_data
- From: Andrew Morton <akpm@linux-foundation.org>
- Re: [PATCH]gx-suspmod.c use boot_cpu_data instead of current_cpu_data
- From: Dave Jones <davej@redhat.com>
- [PATCH]gx-suspmod.c use boot_cpu_data instead of current_cpu_data
- Prev by Date: Re: 2.6.23-rc1: no setup signature found...
- Next by Date: [patch] x86 boot code comments typos
- Previous by thread: Re: [PATCH]gx-suspmod.c use boot_cpu_data instead of current_cpu_data
- Next by thread: Re: [PATCH]gx-suspmod.c use boot_cpu_data instead of current_cpu_data
- Index(es):
 |