All of lore.kernel.org
 help / color / mirror / Atom feed
From: Abel Vesa <abelvesa@gmail.com>
To: mturquette@linaro.org, peterz@infradead.org, mingo@kernel.org
Cc: linux-kernel@vger.kernel.org, patches@linaro.org,
	Abel Vesa <abelvesa@gmail.com>
Subject: [PATCH] sched/core: Add empty 'gov_cfs_update_cpu' function definition for NON-SMP systems
Date: Tue,  5 May 2015 23:57:37 +0300	[thread overview]
Message-ID: <1430859457-11304-1-git-send-email-abelvesa@gmail.com> (raw)

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 <abelvesa@gmail.com>
---
 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


             reply	other threads:[~2015-05-05 20:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-05 20:57 Abel Vesa [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-05-04 22:10 [PATCH 0/4] scheduler-based cpu frequency scaling Michael Turquette
2015-05-06 16:50 ` [PATCH] sched/core: Add empty 'gov_cfs_update_cpu' function definition for NON-SMP systems Abel Vesa
2015-05-07  4:18   ` Michael Turquette

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1430859457-11304-1-git-send-email-abelvesa@gmail.com \
    --to=abelvesa@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mturquette@linaro.org \
    --cc=patches@linaro.org \
    --cc=peterz@infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.