From: gadiyar@ti.com (Gadiyar, Anand)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] arm/clkdev: Allow common struct clk usage
Date: Tue, 3 Aug 2010 09:47:33 +0530 [thread overview]
Message-ID: <5A47E75E594F054BAF48C5E4FC4B92AB032194B826@dbde02.ent.ti.com> (raw)
In-Reply-To: <1280473404.511776.487110192782.3.gpush@pororo>
Jeremy Kerr wrote:
> A couple of small changes to allow the common struct clk infrastructure
> on ARM. The common clock API provides clk_put, and we no longer need
> mach/clkdev.h (as we don't need __clk_put anymore).
>
> Signed-off-by: Jeremy Kerr <jeremy.kerr@canonical.com>
>
> ---
> arch/arm/common/clkdev.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/arch/arm/common/clkdev.c b/arch/arm/common/clkdev.c
> index e2b2bb6..d7dc1f8 100644
> --- a/arch/arm/common/clkdev.c
> +++ b/arch/arm/common/clkdev.c
<snip>
> @@ -87,14 +90,21 @@ struct clk *clk_get(struct device *dev,
> const char *con_id)
> }
> EXPORT_SYMBOL(clk_get);
>
> +#ifndef CONFIG_USE_COMMON_STRUCT_CLK
> +/* For the common struct clk case, clk_put is provided by the kernel-wide
> + * API. */
Minor coding-style comment. The preferred style for multi-line
comments is:
/*
* For the common ...
* API.
*/
- Anand
next prev parent reply other threads:[~2010-08-03 4:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-30 7:03 [PATCH 0/3] Common struct clk implementation, v6 Jeremy Kerr
2010-07-30 7:03 ` [PATCH 1/3] Add a common struct clk Jeremy Kerr
2010-07-30 7:03 ` [PATCH 3/3] arm/clkdev: Allow common struct clk usage Jeremy Kerr
2010-08-03 4:17 ` Gadiyar, Anand [this message]
2010-07-30 7:03 ` [PATCH 2/3] clk: Generic support for fixed-rate clocks Jeremy Kerr
-- strict thread matches above, loose matches on Subject: below --
2010-09-15 3:40 [PATCH 0/3] Common struct clk implementation, v7 Jeremy Kerr
2010-09-15 3:40 ` [PATCH 3/3] arm/clkdev: Allow common struct clk usage Jeremy Kerr
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=5A47E75E594F054BAF48C5E4FC4B92AB032194B826@dbde02.ent.ti.com \
--to=gadiyar@ti.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