Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756404AbbLHNL3 (ORCPT ); Tue, 8 Dec 2015 08:11:29 -0500 Received: from smtprelay.synopsys.com ([198.182.60.111]:36040 "EHLO smtprelay.synopsys.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756131AbbLHNL1 (ORCPT ); Tue, 8 Dec 2015 08:11:27 -0500 From: Vineet Gupta To: Ingo Molnar , Peter Zijlstra , Thomas Gleixner CC: , , Vineet Gupta Subject: [PATCH] sched/fair: [cosmetic] match ifdef/endif CONFIG_NO_HZ_COMMON Date: Tue, 8 Dec 2015 18:41:05 +0530 Message-ID: <1449580265-8532-1-git-send-email-vgupta@synopsys.com> X-Mailer: git-send-email 1.9.1 MIME-Version: 1.0 Content-Type: text/plain X-Originating-IP: [10.12.197.182] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 936 Lines: 32 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 --- 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 majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/