On 05/15/2015 05:09 AM, Viresh Kumar wrote:
On 15 May 2015 at 01:45, Rafael J. Wysocki wrote:
You need ACKs from Viresh for those two, then. He's officially responsible
for ARM cpufreq drivers.
I thought an Ack for 14th is enough :)
For: 12/13/14.
Acked-by: Viresh Kumar
Thanks! :)
It p
On 15 May 2015 at 01:45, Rafael J. Wysocki wrote:
> You need ACKs from Viresh for those two, then. He's officially responsible
> for ARM cpufreq drivers.
I thought an Ack for 14th is enough :)
For: 12/13/14.
Acked-by: Viresh Kumar
--
To unsubscribe from this list: send the line "unsubscribe li
On Thursday, May 14, 2015 09:15:11 AM Mikko Perttunen wrote:
> On 05/14/2015 01:47 AM, Rafael J. Wysocki wrote:
> > ...
> >
> > If I'm supposed to apply this, I need ACKs from the appropriate people on
> > all the patches where they are still missing. Thanks!
> >
> >
>
> I believe Thierry Reding
On 05/14/2015 01:47 AM, Rafael J. Wysocki wrote:
> ...
If I'm supposed to apply this, I need ACKs from the appropriate people on
all the patches where they are still missing. Thanks!
I believe Thierry Reding will apply the series; your ACK as cpufreq
maintainer for patch 13, and maybe also
On Wednesday, May 13, 2015 05:58:34 PM Mikko Perttunen wrote:
> v9 of the Tegra124 cpufreq series. Changes:
>
> - Dropped PLLX reordering patch since it is no longer needed
> - Removed a couple of unused lines from the DFLL clocksource platform driver
> - Made the cpufreq driver tristate and remov
v9 of the Tegra124 cpufreq series. Changes:
- Dropped PLLX reordering patch since it is no longer needed
- Removed a couple of unused lines from the DFLL clocksource platform driver
- Made the cpufreq driver tristate and removed .owned = THIS_MODULE (as it's
not needed for
platform devices)
- M
6 matches
Mail list logo
