The patch titled
lockdep: use BUILD_BUG_ON
has been added to the -mm tree. Its filename is
lockdep-use-build_bug_on.patch
See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
out what to do about this
------------------------------------------------------
Subject: lockdep: use BUILD_BUG_ON
From: Alexey Dobriyan <adobriyan@xxxxxxxxx>
Signed-off-by: Alexey Dobriyan <adobriyan@xxxxxxxxx>
Cc: Ingo Molnar <mingo@xxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxx>
---
kernel/lockdep.c | 5 +----
1 file changed, 1 insertion(+), 4 deletions(-)
diff -puN kernel/lockdep.c~lockdep-use-build_bug_on kernel/lockdep.c
--- a/kernel/lockdep.c~lockdep-use-build_bug_on
+++ a/kernel/lockdep.c
@@ -1114,8 +1114,6 @@ static int count_matching_names(struct l
return count + 1;
}
-extern void __error_too_big_MAX_LOCKDEP_SUBCLASSES(void);
-
/*
* Register a lock's class in the hash-table, if the class is not present
* yet. Otherwise we look it up. We cache the result in the lock object
@@ -1153,8 +1151,7 @@ look_up_lock_class(struct lockdep_map *l
* (or spin_lock_init()) call - which acts as the key. For static
* locks we use the lock object itself as the key.
*/
- if (sizeof(struct lock_class_key) > sizeof(struct lock_class))
- __error_too_big_MAX_LOCKDEP_SUBCLASSES();
+ BUILD_BUG_ON(sizeof(struct lock_class_key) > sizeof(struct lock_class));
key = lock->key->subkeys + subclass;
_
Patches currently in -mm which might be from adobriyan@xxxxxxxxx are
asus_acpi-fix-proc-files-parsing.patch
asus_acpi-dont-printk-on-writing-garbage-to-proc-files.patch
git-gfs2.patch
config_pm=n-slim-drivers-pcmcia.patch
i82092-wire-up-errors-from-pci_register_driver.patch
megaraid-fix-warnings-when-config_proc_fs=n.patch
scsi_libc-use-build_bug_on.patch
drivers-usb-net-use-build_bug_on.patch
prism54-use-build_bug_on.patch
fs-use-build_bug_on.patch
dac960-use-memmove-for-overlapping-areas.patch
lockdep-use-build_bug_on.patch
md-use-build_bug_on.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
