fix cpu_chain section mismatch...
authorDaniel J Blueman <daniel.blueman@gmail.com>
Tue, 1 Jun 2010 11:15:11 +0000 (12:15 +0100)
committerLinus Torvalds <torvalds@linux-foundation.org>
Tue, 1 Jun 2010 16:22:50 +0000 (09:22 -0700)
In commit e9fb7631ebcd ("cpu-hotplug: introduce cpu_notify(),
__cpu_notify(), cpu_notify_nofail()") the new helper functions access
cpu_chain.  As a result, it shouldn't be marked __cpuinitdata (via
section mismatch warning).

Alternatively, the helper functions should be forced inline, or marked
__ref or __cpuinit.  In the meantime, this patch silences the warning
the trivial way.

Signed-off-by: Daniel J Blueman <daniel.blueman@gmail.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
kernel/cpu.c

index 8b92539b4754274528fdc380d45baf6d481001b1..97d1b426a4ac39bd49b41b9393ed9b565f8f7f33 100644 (file)
@@ -34,7 +34,7 @@ void cpu_maps_update_done(void)
        mutex_unlock(&cpu_add_remove_lock);
 }
 
-static __cpuinitdata RAW_NOTIFIER_HEAD(cpu_chain);
+static RAW_NOTIFIER_HEAD(cpu_chain);
 
 /* If set, cpu_up and cpu_down will return -EBUSY and do nothing.
  * Should always be manipulated under cpu_add_remove_lock