From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/4] clk: select CLKDEV_LOOKUP for COMMON_CLK
Date: Sat, 14 Apr 2012 22:18:01 -0500 [thread overview]
Message-ID: <4F8A3DE9.8030008@gmail.com> (raw)
In-Reply-To: <1334003101-17274-2-git-send-email-robherring2@gmail.com>
Mike,
On 04/09/2012 03:24 PM, Rob Herring wrote:
> From: Rob Herring <rob.herring@calxeda.com>
>
> Using the common clock infrastructure without the common clkdev code makes
> little sense, so select CLKDEV_LOOKUP for COMMON_CLK.
>
> Signed-off-by: Rob Herring <rob.herring@calxeda.com>
> ---
Can you apply the 1st 2 patches in this series to your clock fixes tree
for 3.4?
Rob
> drivers/clk/Kconfig | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/clk/Kconfig b/drivers/clk/Kconfig
> index 165e1fe..f05a60d 100644
> --- a/drivers/clk/Kconfig
> +++ b/drivers/clk/Kconfig
> @@ -12,6 +12,7 @@ config HAVE_MACH_CLKDEV
> config COMMON_CLK
> bool
> select HAVE_CLK_PREPARE
> + select CLKDEV_LOOKUP
> ---help---
> The common clock framework is a single definition of struct
> clk, useful across many platforms, as well as an
next prev parent reply other threads:[~2012-04-15 3:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-09 20:24 [PATCH 0/4] DT clock binding support Rob Herring
2012-04-09 20:24 ` [PATCH 1/4] clk: select CLKDEV_LOOKUP for COMMON_CLK Rob Herring
2012-04-15 3:18 ` Rob Herring [this message]
2012-04-17 22:13 ` Turquette, Mike
2012-04-18 7:07 ` Sascha Hauer
2012-04-19 14:59 ` Rob Herring
2012-04-19 20:01 ` Turquette, Mike
2012-04-09 20:24 ` [PATCH 2/4] clk: remove trailing whitespace from clk.h Rob Herring
2012-04-19 20:06 ` Turquette, Mike
2012-04-09 20:25 ` [PATCH 3/4] clk: add DT clock binding support Rob Herring
2012-04-10 2:19 ` Shawn Guo
2012-04-10 4:27 ` Fabio Estevam
2012-04-10 12:57 ` Rob Herring
2012-05-01 22:59 ` Mike Turquette
2012-05-14 13:40 ` Rob Herring
2012-04-09 20:25 ` [PATCH 4/4] clk: add DT fixed-clock " Rob Herring
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=4F8A3DE9.8030008@gmail.com \
--to=robherring2@gmail.com \
--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).