From: Jason Cooper <jason@lakedaemon.net>
To: Andrew Lunn <andrew@lunn.ch>
Cc: rjw@sisk.pl, jacmet@sunsite.dk, cpufreq@vger.kernel.org,
linux ARM <linux-arm-kernel@lists.infradead.org>,
viresh.kumar@linaro.org
Subject: Re: [PATCH v3 2/3] arm: kirkwood: Instantiate cpufreq driver
Date: Sun, 26 May 2013 13:59:57 -0400 [thread overview]
Message-ID: <20130526175957.GD31290@titan.lakedaemon.net> (raw)
In-Reply-To: <1359281244-31455-3-git-send-email-andrew@lunn.ch>
On Sun, Jan 27, 2013 at 11:07:23AM +0100, Andrew Lunn wrote:
> Register a platform driver structure for the cpufreq driver.
>
> Signed-off-by: Andrew Lunn <andrew@lunn.ch>
> ---
> arch/arm/Kconfig | 1 +
> arch/arm/mach-kirkwood/board-dt.c | 3 ++-
> arch/arm/mach-kirkwood/common.c | 23 +++++++++++++++++++++
> arch/arm/mach-kirkwood/common.h | 2 ++
> arch/arm/mach-kirkwood/include/mach/bridge-regs.h | 2 ++
> 5 files changed, 30 insertions(+), 1 deletion(-)
Thanks again to Andrew for digging this one up. Applied to mvebu/soc
thx,
Jason.
next prev parent reply other threads:[~2013-05-26 17:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-27 10:07 [PATCH v3 0/3] Kirkwoode cpufreq driver Andrew Lunn
2013-01-27 10:07 ` [PATCH v3 1/3] cpufreq: kirkwood: Add a cpufreq driver for Marvell Kirkwood SoCs Andrew Lunn
2013-01-27 14:49 ` Viresh Kumar
2013-01-27 15:42 ` Andrew Lunn
2013-01-27 16:03 ` Viresh Kumar
2013-01-27 16:25 ` Andrew Lunn
2013-01-27 16:45 ` Viresh Kumar
2013-01-27 17:17 ` Andrew Lunn
2013-01-28 3:19 ` Viresh Kumar
2013-01-27 17:11 ` Russell King - ARM Linux
2013-01-27 17:23 ` Andrew Lunn
2013-01-28 6:41 ` Shawn Guo
2013-01-27 18:20 ` Andrew Lunn
2013-01-27 10:07 ` [PATCH v3 2/3] arm: kirkwood: Instantiate cpufreq driver Andrew Lunn
2013-05-26 17:59 ` Jason Cooper [this message]
2013-01-27 10:07 ` [PATCH v3 3/3] arm: kirkwood: Enable cpufreq and ondemand on kirkwood_defconfig Andrew Lunn
2013-05-26 18:02 ` Jason Cooper
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=20130526175957.GD31290@titan.lakedaemon.net \
--to=jason@lakedaemon.net \
--cc=andrew@lunn.ch \
--cc=cpufreq@vger.kernel.org \
--cc=jacmet@sunsite.dk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=rjw@sisk.pl \
--cc=viresh.kumar@linaro.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