The patch titled
     gx-suspmod.c: use boot_cpu_data instead of current_cpu_data
has been removed from the -mm tree.  Its filename was
     gx-suspmodc-use-boot_cpu_data-instead-of-current_cpu_data.patch

This patch was dropped because it was merged into mainline or a subsystem tree

------------------------------------------------------
Subject: gx-suspmod.c: use boot_cpu_data instead of current_cpu_data
From: Dave Young <[EMAIL PROTECTED]>

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 <[EMAIL PROTECTED]>
Cc: Dave Jones <[EMAIL PROTECTED]>
CC: <[EMAIL PROTECTED]>
Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
---

 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 [EMAIL PROTECTED] are

git-cpufreq.patch
bluetooth-hidp_process_hid_control-remove-unnecessary-parameter-dealing.patch
bluetooth-rfcomm-tty_close-before-destruct.patch

-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to