Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752425AbbEFQuW (ORCPT ); Wed, 6 May 2015 12:50:22 -0400 Received: from mail-wi0-f176.google.com ([209.85.212.176]:36038 "EHLO mail-wi0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752081AbbEFQuR (ORCPT ); Wed, 6 May 2015 12:50:17 -0400 From: Abel Vesa To: mturquette@linaro.org, peterz@infradead.org, mingo@kernel.org Cc: linux-kernel@vger.kernel.org, patches@linaro.org, Abel Vesa Subject: [PATCH] sched/core: Add empty 'gov_cfs_update_cpu' function definition for NON-SMP systems Date: Wed, 6 May 2015 19:50:40 +0300 Message-Id: <1430931040-16233-1-git-send-email-abelvesa@gmail.com> X-Mailer: git-send-email 1.9.1 In-Reply-To: <1430777441-15087-1-git-send-email-mturquette@linaro.org> References: <1430777441-15087-1-git-send-email-mturquette@linaro.org> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1132 Lines: 32 If CONFIG_SMP is not defined the build will fail due to function 'gov_cfs_update_cpu' definition missing. Added empty static inline definition for NON-SMP systems. This patch applies to: https://git.linaro.org/people/mike.turquette/linux.git sched-freq Signed-off-by: Abel Vesa --- kernel/sched/sched.h | 1 + 1 file changed, 1 insertion(+) diff --git a/kernel/sched/sched.h b/kernel/sched/sched.h index ec23523..3d0996e 100644 --- a/kernel/sched/sched.h +++ b/kernel/sched/sched.h @@ -1413,6 +1413,7 @@ static inline void sched_rt_avg_update(struct rq *rq, u64 rt_delta) #else static inline void sched_rt_avg_update(struct rq *rq, u64 rt_delta) { } static inline void sched_avg_update(struct rq *rq) { } +static inline void gov_cfs_update_cpu(int cpu) {} #endif extern void start_bandwidth_timer(struct hrtimer *period_timer, ktime_t period); -- 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/