Prev: Please Read And Respond
Next: [PATCH 1/2] mac8390: propagate error code from request_irq
From: Daniel J Blueman on 1 Jun 2010 07:20
In 2.6.35-rc1, __cpu_notify access cpu_chain, which shouldn't be
marked __cpuinitdata (via section mismatch warning).

Signed-off-by: Daniel J Blueman <daniel.blueman(a)gmail.com>

diff --git a/kernel/cpu.c b/kernel/cpu.c
index 8b92539..97d1b42 100644
--- a/kernel/cpu.c
+++ b/kernel/cpu.c
@@ -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
--
Daniel J Blueman
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: Please Read And Respond
Next: [PATCH 1/2] mac8390: propagate error code from request_irq