Re: [PATCH V2] Fix problem with cpufreq_ondemand or cpufreq_conservative

2013-01-01 Thread Viresh Kumar
On 2 January 2013 09:40, Larry Finger wrote: >>> Index: wireless-testing-new/drivers/cpufreq/cpufreq_governor.c >> >> >> How are you creating these patches? wireless-testing-new (linux directory >> names) >> aren't supposed to be present here. You Missed this one? > I was not adding myself - my

Re: [PATCH V2] Fix problem with cpufreq_ondemand or cpufreq_conservative

2013-01-01 Thread Larry Finger
On 01/01/2013 09:56 PM, Viresh Kumar wrote: I know, V4 is already accepted, but i had an small comment with one of your earlier change, which doesn't exist anymore :) On Sat, Dec 29, 2012 at 5:51 AM, Larry Finger wrote: Index: wireless-testing-new/drivers/cpufreq/cpufreq_governor.c How are y

Re: [PATCH V2] Fix problem with cpufreq_ondemand or cpufreq_conservative

2013-01-01 Thread Viresh Kumar
I know, V4 is already accepted, but i had an small comment with one of your earlier change, which doesn't exist anymore :) On Sat, Dec 29, 2012 at 5:51 AM, Larry Finger wrote: > Index: wireless-testing-new/drivers/cpufreq/cpufreq_governor.c How are you creating these patches? wireless-testing-ne

[PATCH V2] Fix problem with cpufreq_ondemand or cpufreq_conservative

2012-12-28 Thread Larry Finger
Since commit 2aacdff entitled "cpufreq: Move common part from governors to separate file", whenever the drivers that depend on this new file (cpufreq_ondemand or cpufreq_conservative) are built as modules, a new module named cpufreq_governor is created. It seems that kmake is smart enough to crea