On 9 October 2014 05:31, Mike Turquette wrote:
> Whether you merge the patches now or later is fine by me. I prefer to
> get my patches out early and often so I can avoid any surprises later
> on. If you have a fundamental objection to these patches then please let
> me know. Otherwise it would
Quoting Viresh Kumar (2014-10-08 01:19:40)
> On 8 October 2014 13:41, Thomas Petazzoni
> wrote:
> > On Wed, 8 Oct 2014 13:24:30 +0530, Viresh Kumar wrote:
> >> On 8 October 2014 13:18, Mike Turquette wrote:
>
> >> > This series is partially in response to a discussion around DT bindings
> >> >
On 8 October 2014 13:41, Thomas Petazzoni
wrote:
> On Wed, 8 Oct 2014 13:24:30 +0530, Viresh Kumar wrote:
>> On 8 October 2014 13:18, Mike Turquette wrote:
>> > This series is partially in response to a discussion around DT bindings
>> > for CPUfreq drivers [0], but it is also needed for
Dear Viresh Kumar,
On Wed, 8 Oct 2014 13:24:30 +0530, Viresh Kumar wrote:
> On 8 October 2014 13:18, Mike Turquette wrote:
> > This series is partially in response to a discussion around DT bindings
> > for CPUfreq drivers [0], but it is also needed for on-going work to
> > integrate CPUfreq
On 8 October 2014 13:18, Mike Turquette wrote:
> This series is partially in response to a discussion around DT bindings
> for CPUfreq drivers [0], but it is also needed for on-going work to
> integrate CPUfreq with the scheduler. In particular a scheduler-driven
> cpu frequency scaling policy
This series is partially in response to a discussion around DT bindings
for CPUfreq drivers [0], but it is also needed for on-going work to
integrate CPUfreq with the scheduler. In particular a scheduler-driven
cpu frequency scaling policy would be well served to know if the
underlying CPUfreq
This series is partially in response to a discussion around DT bindings
for CPUfreq drivers [0], but it is also needed for on-going work to
integrate CPUfreq with the scheduler. In particular a scheduler-driven
cpu frequency scaling policy would be well served to know if the
underlying CPUfreq
On 8 October 2014 13:18, Mike Turquette mturque...@linaro.org wrote:
This series is partially in response to a discussion around DT bindings
for CPUfreq drivers [0], but it is also needed for on-going work to
integrate CPUfreq with the scheduler. In particular a scheduler-driven
cpu frequency
Dear Viresh Kumar,
On Wed, 8 Oct 2014 13:24:30 +0530, Viresh Kumar wrote:
On 8 October 2014 13:18, Mike Turquette mturque...@linaro.org wrote:
This series is partially in response to a discussion around DT bindings
for CPUfreq drivers [0], but it is also needed for on-going work to
On 8 October 2014 13:41, Thomas Petazzoni
thomas.petazz...@free-electrons.com wrote:
On Wed, 8 Oct 2014 13:24:30 +0530, Viresh Kumar wrote:
On 8 October 2014 13:18, Mike Turquette mturque...@linaro.org wrote:
This series is partially in response to a discussion around DT bindings
for
Quoting Viresh Kumar (2014-10-08 01:19:40)
On 8 October 2014 13:41, Thomas Petazzoni
thomas.petazz...@free-electrons.com wrote:
On Wed, 8 Oct 2014 13:24:30 +0530, Viresh Kumar wrote:
On 8 October 2014 13:18, Mike Turquette mturque...@linaro.org wrote:
This series is partially in
On 9 October 2014 05:31, Mike Turquette mturque...@linaro.org wrote:
Whether you merge the patches now or later is fine by me. I prefer to
get my patches out early and often so I can avoid any surprises later
on. If you have a fundamental objection to these patches then please let
me know.
12 matches
Mail list logo
