Re: Potential cpufreq backports for v3.10 LTS

Mark Brown <[email protected]> Tue, 7 Oct 2014 23:50:06 +0100

Newsgroups	org.kernel.vger.cpufreq,org.kernel.vger.linux-pm
Message-ID	<[email protected]>

On Tue, Oct 07, 2014 at 02:58:07PM -0700, Greg Kroah-Hartman wrote:
> On Tue, Oct 07, 2014 at 09:45:05PM +0100, Mark Brown wrote:

> > Actually I thinkoed here, as I said in reply to the stable mail the
> > problematic patch was "19c763031acb8 cpufreq: serialize calls to
> > __cpufreq_governor()" which was reverted in "56d07db cpufreq: Remove
> > temporary fix for race between CPU hotplug and sysfs-writes".  The above
> > commit ID (95731eb) should be good.

> > Sorry about the confusion here.

> Ok, I'm still confused.  I've applied 3 patches to the 3.10-stable
> queue, in this order:

To the best of my ability to assess:

> 	19c763031acb831a5ab9c1a701b7fedda073eb3f	cpufreq: serialize calls to __cpufreq_governor()

This one is bad.

> 	a857c0b9e24e39fe5be82451b65377795f9538d8	cpufreq: Fix wrong time unit conversion
> 	dfa5bb622555d9da0df21b50f46ebdeef390041b	cpufreq: ondemand: Change the calculation of target frequency

These two should be good.

> Are those correct?  Is there anything else I need to apply?

> Note, 95731eb does not apply to 3.10-stable as it is already in there,
> it showed up in 3.10.37.

Ah, good - I think whatever made my cut'n'paste of the commit ID go
wrong will have been responsible for making my search for it fail.

signature.asc (application/pgp-signature, 473 B)