Spotted this when debuggign something completely different and trying to
unravel CONFIG_NO_HZ{,_COMMON,,_IDLE}It seems we can clean up the legacy CONFIG_NO_HZ option, but first remove it's proliferation. Signed-off-by: Vineet Gupta <[email protected]> --- kernel/sched/fair.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c index f04fda8f669c..0995a3dccd58 100644 --- a/kernel/sched/fair.c +++ b/kernel/sched/fair.c @@ -4408,7 +4408,7 @@ void update_cpu_load_nohz(void) } raw_spin_unlock(&this_rq->lock); } -#endif /* CONFIG_NO_HZ */ +#endif /* CONFIG_NO_HZ_COMMON */ /* * Called from scheduler_tick() -- 1.9.1 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
