Re: Potential cpufreq backports for v3.10 LTS

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Oct 07, 2014 at 11:50:06PM +0100, Mark Brown wrote:
> 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.

Ok, now deleted, thanks for letting me know.

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Kernel]     [Kernel Development Newbies]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]