From: "Sören Brinkmann" <soren.brinkmann@xilinx.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>,
Michal Simek <michal.simek@xilinx.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v4 0/4] ARM: zynq: cpufreq support
Date: Thu, 27 Feb 2014 09:52:17 -0800 [thread overview]
Message-ID: <3402bb7c-3dec-403a-9356-65af803e1b0a@AM1EHSMHS017.ehs.local> (raw)
In-Reply-To: <1392851684-29950-1-git-send-email-soren.brinkmann@xilinx.com>
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.
Thanks,
Sören
next prev parent reply other threads:[~2014-02-27 17:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 23:14 Soren Brinkmann
2014-02-19 23:14 ` [PATCH v4 1/4] clocksource/cadence_ttc: Call clockevents_update_freq() with IRQs enabled Soren Brinkmann
2014-02-19 23:14 ` [PATCH v4 2/4] clocksource/cadence_ttc: Overhaul clocksource frequency adjustment Soren Brinkmann
2014-02-19 23:14 ` [PATCH v4 3/4] arm: zynq: Don't use arm_global_timer with cpufreq Soren Brinkmann
2014-02-19 23:14 ` [PATCH v4 4/4] arm: zynq: Add support for cpufreq Soren Brinkmann
2014-02-27 17:52 ` Sören Brinkmann [this message]
2014-02-28 6:58 ` [PATCH v4 0/4] ARM: zynq: cpufreq support Daniel Lezcano
[not found] ` <20140227175217.GW13293@xsjandreislx>
2014-02-28 6:26 ` Michal Simek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3402bb7c-3dec-403a-9356-65af803e1b0a@AM1EHSMHS017.ehs.local \
--to=soren.brinkmann@xilinx.com \
--cc=daniel.lezcano@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@xilinx.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®