The patch titled
gx-suspmod.c: use boot_cpu_data instead of current_cpu_data
has been added to the -mm tree. Its filename is
gx-suspmodc-use-boot_cpu_data-instead-of-current_cpu_data.patch
*** Remember to use Documentation/SubmitChecklist when testing your code ***
See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
out what to do about this
------------------------------------------------------
Subject: gx-suspmod.c: use boot_cpu_data instead of current_cpu_data
From: Dave Young <hidave.darkstar@xxxxxxxxx>
In preemptible kernel will report BUG: using smp_processor_id() in
preemptible, so use boot_cpu_data instead of current_cpu_data.
discussion in :
http://lkml.org/lkml/2007/7/25/32
Signed-off-by: Dave Young <hidave.darkstar@xxxxxxxxx>
Cc: Dave Jones <davej@xxxxxxxxxxxxxxxxx>
CC: <stable@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
arch/x86/kernel/cpu/cpufreq/gx-suspmod.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff -puN arch/x86/kernel/cpu/cpufreq/gx-suspmod.c~gx-suspmodc-use-boot_cpu_data-instead-of-current_cpu_data arch/x86/kernel/cpu/cpufreq/gx-suspmod.c
--- a/arch/x86/kernel/cpu/cpufreq/gx-suspmod.c~gx-suspmodc-use-boot_cpu_data-instead-of-current_cpu_data
+++ a/arch/x86/kernel/cpu/cpufreq/gx-suspmod.c
@@ -181,8 +181,8 @@ static __init struct pci_dev *gx_detect_
struct pci_dev *gx_pci = NULL;
/* check if CPU is a MediaGX or a Geode. */
- if ((current_cpu_data.x86_vendor != X86_VENDOR_NSC) &&
- (current_cpu_data.x86_vendor != X86_VENDOR_CYRIX)) {
+ if ((boot_cpu_data.x86_vendor != X86_VENDOR_NSC) &&
+ (boot_cpu_data.x86_vendor != X86_VENDOR_CYRIX)) {
dprintk("error: no MediaGX/Geode processor found!\n");
return NULL;
}
_
Patches currently in -mm which might be from hidave.darkstar@xxxxxxxxx are
origin.patch
zisofs-use-mutex-instead-of-semaphore.patch
gx-suspmodc-use-boot_cpu_data-instead-of-current_cpu_data.patch
param_sysfs_builtin-memchr-argument-fix.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
