The patch titled
intel_cacheinfo: Call cache_add_dev from cache_sysfs_init explicitly
has been removed from the -mm tree. Its filename was
intel_cacheinfo-call-cache_add_dev-from-cache_sysfs_init.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
Subject: intel_cacheinfo: Call cache_add_dev from cache_sysfs_init explicitly
From: Satyam Sharma <satyam@xxxxxxxxxxxxx>
Call cache_add_dev() from cache_sysfs_init() explicitly, instead of
referencing the CPU notifier callback directly from generic startup code.
Looks cleaner (to me at least) this way, and also makes it possible to use
other tricks to replace __cpuinit{data} annotations, as recently discussed on
this list.
Signed-off-by: Satyam Sharma <satyam@xxxxxxxxxxxxx>
Cc: Andi Kleen <ak@xxxxxxx>
Cc: Venkatesh Pallipadi <venkatesh.pallipadi@xxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
arch/i386/kernel/cpu/intel_cacheinfo.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff -puN arch/i386/kernel/cpu/intel_cacheinfo.c~intel_cacheinfo-call-cache_add_dev-from-cache_sysfs_init arch/i386/kernel/cpu/intel_cacheinfo.c
--- a/arch/x86/kernel/cpu/intel_cacheinfo.c~intel_cacheinfo-call-cache_add_dev-from-cache_sysfs_init
+++ a/arch/x86/kernel/cpu/intel_cacheinfo.c
@@ -794,8 +794,8 @@ static int __cpuinit cache_sysfs_init(vo
register_hotcpu_notifier(&cacheinfo_cpu_notifier);
for_each_online_cpu(i) {
- cacheinfo_cpu_callback(&cacheinfo_cpu_notifier, CPU_ONLINE,
- (void *)(long)i);
+ struct sys_device *sys_dev = get_cpu_sysdev((unsigned int)i);
+ cache_add_dev(sys_dev);
}
return 0;
_
Patches currently in -mm which might be from satyam@xxxxxxxxxxxxx are
origin.patch
git-watchdog.patch
unify-dma_bit_mask-definitions-v31.patch
redefine-unregister_hotcpu_notifier-hotplug_cpu-stubs.patch
x86-msr-driver-misc-cpuinit-annotations.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
