On 24-01-17, 11:00, Juri Lelli wrote:
Hi Viresh,
On 23/01/17 16:51, Viresh Kumar wrote:
From: Steve Muckle smuckle@linaro.org
Upcoming support for scheduler cpufreq callbacks on remote wakeups will require the client to know what the target CPU is that the callback is being invoked for. Add this information into the callback data structure.
Signed-off-by: Steve Muckle smuckle@linaro.org Signed-off-by: Viresh Kumar viresh.kumar@linaro.org
include/linux/sched.h | 1 + kernel/sched/cpufreq.c | 1 + 2 files changed, 2 insertions(+)
diff --git a/include/linux/sched.h b/include/linux/sched.h index ad3ec9ec61f7..8d4409287adf 100644 --- a/include/linux/sched.h +++ b/include/linux/sched.h @@ -3663,6 +3663,7 @@ static inline unsigned long rlimit_max(unsigned int limit) #ifdef CONFIG_CPU_FREQ struct update_util_data { void (*func)(struct update_util_data *data, u64 time, unsigned int flags);
int cpu;
This bit seems to have whitespace damage issues (spaces instead of tabs), can you please check? I'm actually cherry-picking from
ssh://git@git.linaro.org/people/viresh.kumar/linux.git cpufreq/remote-wakeup
and include/linux/sched.h seems to have spaces instead of tabs at the point above.
Thanks for noticing that. Probably Steve was trying to copy how it is done earlier. If you see the earlier line: void (*func)..., it has the same issue. Other places in the file don't have that though.
Anyway, we shall keep tabs going forward. I will fix that one.
-- viresh