From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V6 0/7] add a generic cpufreq driver
Date: Fri, 3 Feb 2012 16:28:44 +0000 [thread overview]
Message-ID: <20120203162844.GO889@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20120109145246.GA2386@richard-laptop>
On Mon, Jan 09, 2012 at 10:52:48PM +0800, Richard Zhao wrote:
> On Fri, Jan 06, 2012 at 08:53:37AM +0800, Richard Zhao wrote:
> > On Thu, Jan 05, 2012 at 06:16:54AM +0800, Richard Zhao wrote:
> > > hi Russell,
> > >
> > > May I have your ACK, you merge it?
> > Russell, ping
> would you have time to look at this patch series?
Sorry, kept missing this. Yes, patch 1 is fine, and _that_ patch alone
gets:
Acked-by: Russell King <rmk+kernel@arm.linux.org.uk>
prev parent reply other threads:[~2012-02-03 16:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-30 2:56 [PATCH V6 0/7] add a generic cpufreq driver Richard Zhao
2011-12-30 2:56 ` [PATCH V6 1/7] ARM: add cpufreq transiton notifier to adjust loops_per_jiffy for smp Richard Zhao
2011-12-30 2:56 ` [PATCH V6 2/7] arm/imx: cpufreq: remove loops_per_jiffy recalculate " Richard Zhao
2012-01-06 0:56 ` Richard Zhao
2012-01-06 13:19 ` Shawn Guo
2011-12-30 2:56 ` [PATCH V6 3/7] cpufreq: OMAP: " Richard Zhao
2012-01-06 1:02 ` Richard Zhao
2011-12-30 2:56 ` [PATCH V6 4/7] cpufreq: add clk-reg cpufreq driver Richard Zhao
2012-01-11 23:22 ` Kevin Hilman
2012-01-12 8:23 ` Richard Zhao
2012-01-12 22:52 ` Kevin Hilman
2012-01-13 17:16 ` Cousson, Benoit
2011-12-30 2:56 ` [PATCH V6 5/7] dts/imx6q: add cpufreq property Richard Zhao
2011-12-30 2:56 ` [PATCH V6 6/7] arm/imx6q: register arm_clk as cpu to clkdev Richard Zhao
2011-12-30 2:56 ` [PATCH V6 7/7] arm/imx6q: select ARCH_HAS_CPUFREQ Richard Zhao
2012-01-04 22:16 ` [PATCH V6 0/7] add a generic cpufreq driver Richard Zhao
2012-01-06 0:53 ` Richard Zhao
2012-01-09 14:52 ` Richard Zhao
2012-02-03 16:28 ` Russell King - ARM Linux [this message]
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=20120203162844.GO889@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).