From: grant.likely@secretlab.ca (Grant Likely)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 1/4] cpufreq: add arm soc generic cpufreq driver
Date: Wed, 18 Jan 2012 13:51:43 -0700 [thread overview]
Message-ID: <20120118205143.GL4223@ponder.secretlab.ca> (raw)
In-Reply-To: <20120118114228.GB22977@sirena.org.uk>
On Wed, Jan 18, 2012 at 11:42:28AM +0000, Mark Brown wrote:
> On Wed, Jan 18, 2012 at 11:39:50AM +0000, Mark Brown wrote:
>
> > This appears to reintroduce the setting of an exact voltage which I'm
> > sure was fixed in previous versions of the patch.
>
> Erk, sorry - it looks like the device tree list has quite a bit of lag
> in moderation and sent out some old patches which I didn't notice. All
> this has been fixed in subsequent verisons.
Yeah, that's my fault. I'm rather a bursty moderator at times.
g.
next prev parent reply other threads:[~2012-01-18 20:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-16 10:30 [PATCH V2 0/4] add arm soc generic cpufreq driver Richard Zhao
2011-12-16 10:30 ` [PATCH V2 1/4] cpufreq: " Richard Zhao
2011-12-16 10:52 ` Jamie Iles
2011-12-16 19:59 ` Bryan Huntsman
2011-12-17 8:39 ` Richard Zhao
2011-12-19 1:03 ` Richard Zhao
2011-12-19 17:42 ` Stephen Boyd
2011-12-17 8:29 ` Richard Zhao
2011-12-16 11:26 ` Heiko Stübner
2011-12-17 7:57 ` Richard Zhao
2011-12-16 14:32 ` Rob Herring
2011-12-17 8:00 ` Richard Zhao
2011-12-17 9:29 ` Arnd Bergmann
2011-12-18 12:34 ` Richard Zhao
2011-12-20 14:41 ` Mark Brown
2012-01-18 11:39 ` Mark Brown
2012-01-18 11:42 ` Mark Brown
2012-01-18 20:51 ` Grant Likely [this message]
2011-12-16 10:31 ` [PATCH V2 2/4] dts/imx6q: add cpufreq property Richard Zhao
2011-12-16 10:31 ` [PATCH V2 3/4] arm/imx6q: register arm_clk as cpu to clkdev Richard Zhao
2011-12-16 16:35 ` Mark Langsdorf
2011-12-17 7:56 ` Richard Zhao
2011-12-16 10:31 ` [PATCH V2 4/4] arm/imx6q: select ARCH_HAS_CPUFREQ Richard Zhao
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=20120118205143.GL4223@ponder.secretlab.ca \
--to=grant.likely@secretlab.ca \
--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).