[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Mon, 9 Sep 2013 17:11:10 +0200 (CEST)
From: Guennadi Liakhovetski <g.liakhovetski@....de>
To: Viresh Kumar <viresh.kumar@...aro.org>
cc: Greg KH <greg@...ah.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-pm@...r.kernel.org, cpufreq@...r.kernel.org,
linux-sh@...r.kernel.org, Magnus Damm <magnus.damm@...il.com>
Subject: "cpufreq: fix serialization issues with freq change notifiers" breaks
cpufreq too
Sorry guys, I'm trying my best to stop this patch from propagating to
stable and to get it fixed asap, so, the CC list might be a bit excessive.
Also trying to fix the originally spare cc list, which makes it impossible
for me to reply to the original thread, instead have to start a new one.
Commit
commit dceff5ce18801dddc220d6238628619c93bc3cb6
Author: Viresh Kumar <viresh.kumar@...aro.org>
Date: Sun Sep 1 22:19:37 2013 +0530
cpufreq: fix serialization issues with freq change notifiers
breaks .transition_ongoing counting. This leads to cpufreq-cpu0 not
working any more. In particular switching the governor from performance to
powersave directly after boot doesn't result in a frequency switch any
more. Reverting this patch fixes the problem again. Tested with today's
-next.
Please, refrain from including into "stable" until clarified!
Thanks
Guennadi
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists