From: Viresh Kumar Date: Thu, 4 Dec 2014 04:11:51 +0000 (+0530) Subject: thermal: cpu_cooling: no need to set cpufreq_state to zero X-Git-Url: https://git.stricted.de/?a=commitdiff_plain;h=92e615ec82c0314fb480eeb19396f4ac15bf97ef;p=GitHub%2Fmoto-9609%2Fandroid_kernel_motorola_exynos9610.git thermal: cpu_cooling: no need to set cpufreq_state to zero Its already zero, we allocated cpufreq_dev with kzalloc. Signed-off-by: Viresh Kumar Signed-off-by: Eduardo Valentin --- diff --git a/drivers/thermal/cpu_cooling.c b/drivers/thermal/cpu_cooling.c index 537856127f78..30e2ecbb75a7 100644 --- a/drivers/thermal/cpu_cooling.c +++ b/drivers/thermal/cpu_cooling.c @@ -499,7 +499,7 @@ __cpufreq_cooling_register(struct device_node *np, return cool_dev; } cpufreq_dev->cool_dev = cool_dev; - cpufreq_dev->cpufreq_state = 0; + mutex_lock(&cooling_cpufreq_lock); /* Register the notifier for first cpufreq cooling device */