The patch titled
Subject: lib-gcd-use-binary-gcd-algorithm-instead-of-euclidean-fix
has been removed from the -mm tree. Its filename was
lib-gcd-use-binary-gcd-algorithm-instead-of-euclidean-fix.patch
This patch was dropped because it was folded into lib-gcd-use-binary-gcd-algorithm-instead-of-euclidean.patch
------------------------------------------------------
From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
Subject: lib-gcd-use-binary-gcd-algorithm-instead-of-euclidean-fix
avoid #defining a CONFIG_ variable
Cc: George Spelvin <linux@xxxxxxxxxxx>
Cc: Zhaoxiu Zeng <zhaoxiu.zeng@xxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
arch/mips/include/asm/cpu-features.h | 2 +-
lib/gcd.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff -puN arch/mips/include/asm/cpu-features.h~lib-gcd-use-binary-gcd-algorithm-instead-of-euclidean-fix arch/mips/include/asm/cpu-features.h
--- a/arch/mips/include/asm/cpu-features.h~lib-gcd-use-binary-gcd-algorithm-instead-of-euclidean-fix
+++ a/arch/mips/include/asm/cpu-features.h
@@ -187,7 +187,7 @@
(defined(cpu_has_mips64r1) && cpu_has_mips64r1) || \
(defined(cpu_has_mips64r2) && cpu_has_mips64r2) || \
(defined(cpu_has_mips64r6) && cpu_has_mips64r6))
-#define CONFIG_CPU_NO_EFFICIENT_FFS 1
+#define CPU_NO_EFFICIENT_FFS 1
#endif
#ifndef cpu_has_mips_1
diff -puN lib/gcd.c~lib-gcd-use-binary-gcd-algorithm-instead-of-euclidean-fix lib/gcd.c
--- a/lib/gcd.c~lib-gcd-use-binary-gcd-algorithm-instead-of-euclidean-fix
+++ a/lib/gcd.c
@@ -10,7 +10,7 @@
* has decent hardware division.
*/
-#if !defined(CONFIG_CPU_NO_EFFICIENT_FFS)
+#if !defined(CONFIG_CPU_NO_EFFICIENT_FFS) && !defined(CPU_NO_EFFICIENT_FFS)
/* If __ffs is available, the even/odd algorithm benchmarks slower. */
unsigned long gcd(unsigned long a, unsigned long b)
_
Patches currently in -mm which might be from akpm@xxxxxxxxxxxxxxxxxxxx are
lib-gcd-use-binary-gcd-algorithm-instead-of-euclidean.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
