Re: [PATCH] cpufreq: remove sysfs link when a cpu != policy->cpu, is removed

2014-04-07 Thread Viresh Kumar
On 7 April 2014 22:45, Sören Brinkmann wrote: > I see this on 3.13 too (in our vendor tree, but I think mainline would > show the behavior as well). It probably worth to add it into the 3.13 > stable kernel. Thanks.. Patch sent for stable tree. -- To unsubscribe from this list: send the line "uns

Re: [PATCH] cpufreq: remove sysfs link when a cpu != policy->cpu, is removed

2014-04-07 Thread Sören Brinkmann
On Mon, 2014-02-17 at 11:03PM +0100, Rafael J. Wysocki wrote: > On Monday, February 17, 2014 02:52:11 PM Viresh Kumar wrote: > > Earlier patch tried to do this but missed this piece of code to fix. > > > > 42f921a cpufreq: remove sysfs files for CPUs which failed to come back after > > resume > >

Re: [PATCH] cpufreq: remove sysfs link when a cpu != policy->cpu, is removed

2014-02-18 Thread Stephen Warren
On 02/17/2014 02:22 AM, Viresh Kumar wrote: > Earlier patch tried to do this but missed this piece of code to fix. > > 42f921a cpufreq: remove sysfs files for CPUs which failed to come back after > resume > > Currently we are getting this on suspend/resume: > > [ cut here ]--

Re: [PATCH] cpufreq: remove sysfs link when a cpu != policy->cpu, is removed

2014-02-17 Thread Rafael J. Wysocki
On Monday, February 17, 2014 02:52:11 PM Viresh Kumar wrote: > Earlier patch tried to do this but missed this piece of code to fix. > > 42f921a cpufreq: remove sysfs files for CPUs which failed to come back after > resume > > Currently we are getting this on suspend/resume: > > [ cut

[PATCH] cpufreq: remove sysfs link when a cpu != policy->cpu, is removed

2014-02-17 Thread Viresh Kumar
Earlier patch tried to do this but missed this piece of code to fix. 42f921a cpufreq: remove sysfs files for CPUs which failed to come back after resume Currently we are getting this on suspend/resume: [ cut here ] WARNING: CPU: 0 PID: 877 at fs/sysfs/dir.c:52 sysfs_warn_