Re: Potential cpufreq backports for v3.10 LTS

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

 



Hi,

On 07/10/2014 11:04 μμ, Greg Kroah-Hartman wrote:
> On Tue, Oct 07, 2014 at 06:08:00PM +0100, Mark Brown wrote:
>> On Tue, Oct 07, 2014 at 09:46:43AM -0700, Greg Kroah-Hartman wrote:
>>> On Tue, Oct 07, 2014 at 12:48:44PM +0100, Mark Brown wrote:
>>
>>>> The power management team at Linaro has had a look at the cpufreq
>>>> updates since the v3.10 LTS and identified a few patches that look
>>>> like they should be in there.  The most recent of these is from v3.12 so
>>>> they won't apply to any of the more recent stable kernels.
>>
>>>>  - 59a6342203a7a cpufreq: Fix governor start/stop race condition
>>
>>>>    This looks like a straight race condition fix.
>>
>>> That is not a commit id in Linus's tree :(
>>
>> Interesting, I was able to cherry-pick it...  looks like the upstream
>> version is 95731eb.  In any case at roughly the same time you sent your
>> mail it's been drawn to my attention off-list that this was subsequently
>> reverted so please ignore this one.  The others should be fine though.
> 
> Ok, I've queued the others up now.
> 

For your information, commits:

- 61c63e5ed3b9 cpufreq: Remove unused APERF/MPERF support
- cffe4e0e7413 cpufreq: Remove unused function __cpufreq_driver_getavg()

remove unused code (no other functional changes) as a result of
commit dfa5bb622555. They all were part of the same patch set.

I'm not familiar with the procedure of patch inclusion in stable trees,
so please forgive me if this mail is just noise.


Thanks,
Stratos

--
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]