The patch titled
LOG2: Make powerpc's __ilog2_u64() take a 64-bit argument
has been removed from the -mm tree. Its filename was
log2-make-powerpcs-__ilog2_u64-take-a-64-bit-argument.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
Subject: LOG2: Make powerpc's __ilog2_u64() take a 64-bit argument
From: David Howells <dhowells@xxxxxxxxxx>
Make powerpc's __ilog2_u64() take a 64-bit argument.
Signed-off-by: David Howells <dhowells@xxxxxxxxxx>
Cc: Paul Mackerras <paulus@xxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxx>
---
include/asm-powerpc/bitops.h | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
diff -puN include/asm-powerpc/bitops.h~log2-make-powerpcs-__ilog2_u64-take-a-64-bit-argument include/asm-powerpc/bitops.h
--- a/include/asm-powerpc/bitops.h~log2-make-powerpcs-__ilog2_u64-take-a-64-bit-argument
+++ a/include/asm-powerpc/bitops.h
@@ -209,7 +209,7 @@ int __ilog2_u32(u32 n)
#ifdef __powerpc64__
static inline __attribute__((const))
-int __ilog2_u64(u32 n)
+int __ilog2_u64(u64 n)
{
int bit;
asm ("cntlzd %0,%1" : "=r" (bit) : "r" (n));
_
Patches currently in -mm which might be from dhowells@xxxxxxxxxx are
origin.patch
fix-more-workqueue-build-breakage-tps65010.patch
infiniband-work-around-gcc-bug-on-sparc64.patch
workstruct-add-assign_bits-to-give-an-atomic-bitops-safe-assignment.patch
workstruct-use-bitops-safe-direct-assignment.patch
alsa-workqueue-fixes.patch
nfs-represent-64-bit-fileids-as-64-bit-inode-numbers-on-32-bit-systems.patch
pm-fix-smp-races-in-the-freezer.patch
doc-atomic_add_unless-doesnt-imply-mb-on-failure.patch
ecryptfs-public-key-transport-mechanism.patch
ecryptfs-public-key-packet-management.patch
workstruct-implement-generic-up-cmpxchg-where-an-arch-doesnt-support-it.patch
workqueue-dont-hold-workqueue_mutex-in-flush_scheduled_work.patch
reiser4-get_sb_dev-fix.patch
mutex-subsystem-synchro-test-module.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
