Re: [PATCH 00/16] cpufreq: create & use cpufreq_generic_get() routine

2013-08-25 Thread Viresh Kumar
On 24 August 2013 20:20, Rafael J. Wysocki  wrote:
> OK, let me rephrase that more directly: Please, slow down.  Allow your 
> previous
> changes to be integrated before you throw more of them at people.

Okay, I will try :)

Btw, Are you going to take any of my patches for 3.12?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [PATCH 00/16] cpufreq: create use cpufreq_generic_get() routine

2013-08-25 Thread Viresh Kumar
On 24 August 2013 20:20, Rafael J. Wysocki r...@sisk.pl wrote:
 OK, let me rephrase that more directly: Please, slow down.  Allow your 
 previous
 changes to be integrated before you throw more of them at people.

Okay, I will try :)

Btw, Are you going to take any of my patches for 3.12?
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [PATCH 00/16] cpufreq: create & use cpufreq_generic_get() routine

2013-08-24 Thread Rafael J. Wysocki
On Saturday, August 24, 2013 09:50:06 AM Viresh Kumar wrote:
> On 24 August 2013 01:10, Rafael J. Wysocki  wrote:
> > On Friday, August 23, 2013 09:20:35 PM Viresh Kumar wrote:
> >> CPUFreq drivers that use clock frameworks interface,i.e. clk_get_rate(), 
> >> to get
> >> CPUs clk rate, has similar sort of code used for most of them.
> >>
> >> This patchset adds a generic ->get() which will do the same thing for 
> >> them. All
> >> those drivers are required to now is to set .get to cpufreq_generic_get() 
> >> and
> >> set their clk pointer in policy->clk during ->init().
> >>
> >> Later part of this patchset fixes 17 drivers with this change.
> >>
> >> That's part 7 of my generic cleanups for CPUFreq core, first six are here:
> >
> > And that's the last one for 3.13, right?
> 
> 3.13 is too far, can't promise that really :)

OK, let me rephrase that more directly: Please, slow down.  Allow your previous
changes to be integrated before you throw more of them at people.

Thanks,
Rafael

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [PATCH 00/16] cpufreq: create use cpufreq_generic_get() routine

2013-08-24 Thread Rafael J. Wysocki
On Saturday, August 24, 2013 09:50:06 AM Viresh Kumar wrote:
 On 24 August 2013 01:10, Rafael J. Wysocki r...@sisk.pl wrote:
  On Friday, August 23, 2013 09:20:35 PM Viresh Kumar wrote:
  CPUFreq drivers that use clock frameworks interface,i.e. clk_get_rate(), 
  to get
  CPUs clk rate, has similar sort of code used for most of them.
 
  This patchset adds a generic -get() which will do the same thing for 
  them. All
  those drivers are required to now is to set .get to cpufreq_generic_get() 
  and
  set their clk pointer in policy-clk during -init().
 
  Later part of this patchset fixes 17 drivers with this change.
 
  That's part 7 of my generic cleanups for CPUFreq core, first six are here:
 
  And that's the last one for 3.13, right?
 
 3.13 is too far, can't promise that really :)

OK, let me rephrase that more directly: Please, slow down.  Allow your previous
changes to be integrated before you throw more of them at people.

Thanks,
Rafael

--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [PATCH 00/16] cpufreq: create & use cpufreq_generic_get() routine

2013-08-23 Thread Viresh Kumar
On 24 August 2013 01:10, Rafael J. Wysocki  wrote:
> On Friday, August 23, 2013 09:20:35 PM Viresh Kumar wrote:
>> CPUFreq drivers that use clock frameworks interface,i.e. clk_get_rate(), to 
>> get
>> CPUs clk rate, has similar sort of code used for most of them.
>>
>> This patchset adds a generic ->get() which will do the same thing for them. 
>> All
>> those drivers are required to now is to set .get to cpufreq_generic_get() and
>> set their clk pointer in policy->clk during ->init().
>>
>> Later part of this patchset fixes 17 drivers with this change.
>>
>> That's part 7 of my generic cleanups for CPUFreq core, first six are here:
>
> And that's the last one for 3.13, right?

3.13 is too far, can't promise that really :)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [PATCH 00/16] cpufreq: create & use cpufreq_generic_get() routine

2013-08-23 Thread Rafael J. Wysocki
On Friday, August 23, 2013 09:20:35 PM Viresh Kumar wrote:
> CPUFreq drivers that use clock frameworks interface,i.e. clk_get_rate(), to 
> get
> CPUs clk rate, has similar sort of code used for most of them.
> 
> This patchset adds a generic ->get() which will do the same thing for them. 
> All
> those drivers are required to now is to set .get to cpufreq_generic_get() and
> set their clk pointer in policy->clk during ->init().
> 
> Later part of this patchset fixes 17 drivers with this change.
> 
> That's part 7 of my generic cleanups for CPUFreq core, first six are here:

And that's the last one for 3.13, right?

Rafael

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [PATCH 00/16] cpufreq: create use cpufreq_generic_get() routine

2013-08-23 Thread Rafael J. Wysocki
On Friday, August 23, 2013 09:20:35 PM Viresh Kumar wrote:
 CPUFreq drivers that use clock frameworks interface,i.e. clk_get_rate(), to 
 get
 CPUs clk rate, has similar sort of code used for most of them.
 
 This patchset adds a generic -get() which will do the same thing for them. 
 All
 those drivers are required to now is to set .get to cpufreq_generic_get() and
 set their clk pointer in policy-clk during -init().
 
 Later part of this patchset fixes 17 drivers with this change.
 
 That's part 7 of my generic cleanups for CPUFreq core, first six are here:

And that's the last one for 3.13, right?

Rafael

--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [PATCH 00/16] cpufreq: create use cpufreq_generic_get() routine

2013-08-23 Thread Viresh Kumar
On 24 August 2013 01:10, Rafael J. Wysocki r...@sisk.pl wrote:
 On Friday, August 23, 2013 09:20:35 PM Viresh Kumar wrote:
 CPUFreq drivers that use clock frameworks interface,i.e. clk_get_rate(), to 
 get
 CPUs clk rate, has similar sort of code used for most of them.

 This patchset adds a generic -get() which will do the same thing for them. 
 All
 those drivers are required to now is to set .get to cpufreq_generic_get() and
 set their clk pointer in policy-clk during -init().

 Later part of this patchset fixes 17 drivers with this change.

 That's part 7 of my generic cleanups for CPUFreq core, first six are here:

 And that's the last one for 3.13, right?

3.13 is too far, can't promise that really :)
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/