Re: [PATCH V2] cpufreq: Always remove sysfs cpuX/cpufreq link on ->remove_dev()

2015-11-23 Thread Rafael J. Wysocki
On Saturday, November 21, 2015 06:42:09 AM Srinivas Pandruvada wrote: > On Sat, 2015-11-21 at 09:06 +0530, Viresh Kumar wrote: > > Subsys interface's ->remove_dev() is called when the cpufreq driver > > is > > unregistering or the CPU is getting physically removed. We keep > > removing > > the cpuX

Re: [PATCH V2] cpufreq: Always remove sysfs cpuX/cpufreq link on ->remove_dev()

2015-11-21 Thread Srinivas Pandruvada
On Sat, 2015-11-21 at 09:06 +0530, Viresh Kumar wrote: > Subsys interface's ->remove_dev() is called when the cpufreq driver > is > unregistering or the CPU is getting physically removed. We keep > removing > the cpuX/cpufreq link for all CPUs except the last one, which is a > mistake as all CPUs c

[PATCH V2] cpufreq: Always remove sysfs cpuX/cpufreq link on ->remove_dev()

2015-11-20 Thread Viresh Kumar
Subsys interface's ->remove_dev() is called when the cpufreq driver is unregistering or the CPU is getting physically removed. We keep removing the cpuX/cpufreq link for all CPUs except the last one, which is a mistake as all CPUs contain a link now. Because of this, one CPU from each policy will