The patch titled
i386: fix early usage of atomic_add_return and local_add_return on real
i386
has been removed from the -mm tree. Its filename was
i386-fix-early-usage-of-atomic_add_return-and.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
Subject: i386: fix early usage of atomic_add_return and local_add_return on
real i386
From: Thomas Gleixner <[EMAIL PROTECTED]>
The check (boot_cpu_data.x86 == 3) in atomic_add_return() and
local_add_return() fails, when those operations are used before
boot_cpu_data is filled in.
Change the check to (boot_cpu_data.x86 <= 3) to fix this.
Signed-off-by: Thomas Gleixner <[EMAIL PROTECTED]>
Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
---
include/asm-i386/atomic.h | 2 +-
include/asm-i386/local.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff -puN
include/asm-i386/atomic.h~i386-fix-early-usage-of-atomic_add_return-and
include/asm-i386/atomic.h
--- a/include/asm-i386/atomic.h~i386-fix-early-usage-of-atomic_add_return-and
+++ a/include/asm-i386/atomic.h
@@ -182,7 +182,7 @@ static __inline__ int atomic_add_return(
int __i;
#ifdef CONFIG_M386
unsigned long flags;
- if(unlikely(boot_cpu_data.x86==3))
+ if(unlikely(boot_cpu_data.x86 <= 3))
goto no_xadd;
#endif
/* Modern 486+ processor */
diff -puN
include/asm-i386/local.h~i386-fix-early-usage-of-atomic_add_return-and
include/asm-i386/local.h
--- a/include/asm-i386/local.h~i386-fix-early-usage-of-atomic_add_return-and
+++ a/include/asm-i386/local.h
@@ -135,7 +135,7 @@ static __inline__ long local_add_return(
long __i;
#ifdef CONFIG_M386
unsigned long flags;
- if(unlikely(boot_cpu_data.x86==3))
+ if(unlikely(boot_cpu_data.x86 <= 3))
goto no_xadd;
#endif
/* Modern 486+ processor */
_
Patches currently in -mm which might be from [EMAIL PROTECTED] are
git-drm.patch
s390-spinlock-initializer-cleanup.patch
i386-hpet-check-if-the-counter-works.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
