[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2aebf1c5-f0d6-41a9-b6f7-c709ceecc9a1@AM1EHSMHS006.ehs.local>
Date: Fri, 28 Feb 2014 07:26:03 +0100
From: Michal Simek <michal.simek@...inx.com>
To: Sören Brinkmann <soren.brinkmann@...inx.com>
CC: Daniel Lezcano <daniel.lezcano@...aro.org>,
Michal Simek <michal.simek@...inx.com>,
<linux-kernel@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v4 0/4] ARM: zynq: cpufreq support
On 02/27/2014 06:52 PM, Sören Brinkmann wrote:
> Hi Daniel, Michal,
>
> On Wed, 2014-02-19 at 03:14PM -0800, Soren Brinkmann wrote:
>> Hi,
>>
>> another iteration of this series. The patches are the same as in v3, but
>> the series shrank a bit. I rebased this series on tip/timers/core, hence
>> the two patches for the clockevent core fell out, since Thomas already
>> applied those.
>> Additionally I removed the patch 'clocksource/cadence_ttc: Use only one
>> counter'. Thomas brought up some questions regarding that patch which
>> need to be investigated. Since it is not required for the rest of this
>> series, I just dropped it for now.
>>
>> Thanks,
>> Sören
>>
>> Soren Brinkmann (4):
>> clocksource/cadence_ttc: Call clockevents_update_freq() with IRQs
>> enabled
>> clocksource/cadence_ttc: Overhaul clocksource frequency adjustment
>> arm: zynq: Don't use arm_global_timer with cpufreq
>> arm: zynq: Add support for cpufreq
>
> Any comments? I think most of these should be pretty straight forward
> and it would be nice to get some ACKs - or tell me what's wrong. :)
> 'clocksource/cadence_ttc: Overhaul clocksource frequency adjustment'
> might deserve a more thorough review.
No problem from my side.
Daniel?
Thanks,
Michal
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists