Re: [PATCH 00/15] cpufreq: initialize drivers .owner field with THIS_MODULE

2013-08-03 Thread Viresh Kumar
On 31 July 2013 19:49, Viresh Kumar wrote: > CPUFreq core does following at multiple places: > module_{get|put}(cpufreq_driver->owner)). > > This is done to make sure module doesn't get unloaded if it is currently in > use. > This will work only if the .owner field of cpufreq driver is

Re: [PATCH 00/15] cpufreq: initialize drivers .owner field with THIS_MODULE

2013-08-03 Thread Viresh Kumar
On 31 July 2013 19:49, Viresh Kumar viresh.ku...@linaro.org wrote: CPUFreq core does following at multiple places: module_{get|put}(cpufreq_driver-owner)). This is done to make sure module doesn't get unloaded if it is currently in use. This will work only if the .owner field of cpufreq

Re: [PATCH 00/15] cpufreq: initialize drivers .owner field with THIS_MODULE

2013-08-02 Thread Sachin Kamat
On 31 July 2013 22:09, Viresh Kumar wrote: > On 31 July 2013 22:06, Sachin Kamat wrote: >> Hi Viresh, >> >> On 31 July 2013 19:49, Viresh Kumar wrote: >>> CPUFreq core does following at multiple places: >>> module_{get|put}(cpufreq_driver->owner)). >>> >>> This is done to make sure module

Re: [PATCH 00/15] cpufreq: initialize drivers .owner field with THIS_MODULE

2013-08-02 Thread Sachin Kamat
On 31 July 2013 22:09, Viresh Kumar viresh.ku...@linaro.org wrote: On 31 July 2013 22:06, Sachin Kamat sachin.ka...@linaro.org wrote: Hi Viresh, On 31 July 2013 19:49, Viresh Kumar viresh.ku...@linaro.org wrote: CPUFreq core does following at multiple places:

Re: [PATCH 00/15] cpufreq: initialize drivers .owner field with THIS_MODULE

2013-07-31 Thread Viresh Kumar
On 31 July 2013 22:06, Sachin Kamat wrote: > Hi Viresh, > > On 31 July 2013 19:49, Viresh Kumar wrote: >> CPUFreq core does following at multiple places: >> module_{get|put}(cpufreq_driver->owner)). >> >> This is done to make sure module doesn't get unloaded if it is currently in >> use. >>

Re: [PATCH 00/15] cpufreq: initialize drivers .owner field with THIS_MODULE

2013-07-31 Thread Sachin Kamat
Hi Viresh, On 31 July 2013 19:49, Viresh Kumar wrote: > CPUFreq core does following at multiple places: > module_{get|put}(cpufreq_driver->owner)). > > This is done to make sure module doesn't get unloaded if it is currently in > use. > This will work only if the .owner field of cpufreq driver

[PATCH 00/15] cpufreq: initialize drivers .owner field with THIS_MODULE

2013-07-31 Thread Viresh Kumar
CPUFreq core does following at multiple places: module_{get|put}(cpufreq_driver->owner)). This is done to make sure module doesn't get unloaded if it is currently in use. This will work only if the .owner field of cpufreq driver is initialized with a valid pointer. This field wasn't initialized

[PATCH 00/15] cpufreq: initialize drivers .owner field with THIS_MODULE

2013-07-31 Thread Viresh Kumar
CPUFreq core does following at multiple places: module_{get|put}(cpufreq_driver-owner)). This is done to make sure module doesn't get unloaded if it is currently in use. This will work only if the .owner field of cpufreq driver is initialized with a valid pointer. This field wasn't initialized

Re: [PATCH 00/15] cpufreq: initialize drivers .owner field with THIS_MODULE

2013-07-31 Thread Sachin Kamat
Hi Viresh, On 31 July 2013 19:49, Viresh Kumar viresh.ku...@linaro.org wrote: CPUFreq core does following at multiple places: module_{get|put}(cpufreq_driver-owner)). This is done to make sure module doesn't get unloaded if it is currently in use. This will work only if the .owner field of

Re: [PATCH 00/15] cpufreq: initialize drivers .owner field with THIS_MODULE

2013-07-31 Thread Viresh Kumar
On 31 July 2013 22:06, Sachin Kamat sachin.ka...@linaro.org wrote: Hi Viresh, On 31 July 2013 19:49, Viresh Kumar viresh.ku...@linaro.org wrote: CPUFreq core does following at multiple places: module_{get|put}(cpufreq_driver-owner)). This is done to make sure module doesn't get unloaded if