Gitweb:     
http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=c789c037e9d0d93d6081e796ab70b488b2ff69f2
Commit:     c789c037e9d0d93d6081e796ab70b488b2ff69f2
Parent:     0b4b5dde45a9416bf57c1e2e5ccf748e538368aa
Author:     Satyam Sharma <[EMAIL PROTECTED]>
AuthorDate: Wed Oct 17 18:04:40 2007 +0200
Committer:  Thomas Gleixner <[EMAIL PROTECTED]>
CommitDate: Wed Oct 17 20:16:49 2007 +0200

    x86: call cache_add_dev() from cache_sysfs_init() explicitly
    
    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 <[EMAIL PROTECTED]>
    Cc: Andi Kleen <[EMAIL PROTECTED]>
    Cc: Venkatesh Pallipadi <[EMAIL PROTECTED]>
    Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
    Signed-off-by: Ingo Molnar <[EMAIL PROTECTED]>
    Signed-off-by: Thomas Gleixner <[EMAIL PROTECTED]>
---
 arch/x86/kernel/cpu/intel_cacheinfo.c |    5 +++--
 1 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/arch/x86/kernel/cpu/intel_cacheinfo.c 
b/arch/x86/kernel/cpu/intel_cacheinfo.c
index 6f9dd38..1826395 100644
--- a/arch/x86/kernel/cpu/intel_cacheinfo.c
+++ b/arch/x86/kernel/cpu/intel_cacheinfo.c
@@ -794,8 +794,9 @@ static int __cpuinit cache_sysfs_init(void)
        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;
-
To unsubscribe from this list: send the line "unsubscribe git-commits-head" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to