From: Stephen Boyd <sboyd@codeaurora.org>
To: Michael Turquette <mturquette@linaro.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] clk: remove clk-private.h
Date: Fri, 30 Jan 2015 15:48:46 -0800 [thread overview]
Message-ID: <54CC185E.9010007@codeaurora.org> (raw)
In-Reply-To: <1422653113-32688-4-git-send-email-mturquette@linaro.org>
On 01/30/15 13:25, Michael Turquette wrote:
> Private clock framework data structures should be private, surprisingly.
>
> Now that all platforms and drivers have been updated to remove static
> initializations of struct clk and struct clk_core objects and all
> references to clk-private.h have been removed we can move the
> definitions of these structures into drivers/clk/clk.c and delete the
> header.
>
> Additionally the ugly DEFINE_CLK macros have been removed. Those were
> used for static definitions of struct clk objects. That practice is no
> longer allowed.
>
> Signed-off-by: Michael Turquette <mturquette@linaro.org>
This is great!
Reviewed-by: Stephen Boyd <sboyd@codeaurora.org>
given the minor comment below.
> - * Returns 0 on success, otherwise an error code.
> - */
> -int __clk_init(struct device *dev, struct clk *clk);
Shouldn't __clk_init become static now in clk.c?
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2015-01-30 23:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-30 21:25 [PATCH 0/3] remove clk-private.h Michael Turquette
2015-01-30 21:25 ` [PATCH 1/3] arm: omap2+ remove dead clock code Michael Turquette
2015-01-30 21:51 ` Tony Lindgren
2015-01-30 21:25 ` [PATCH 2/3] pci: xgene: do not use clk-private.h Michael Turquette
2015-01-30 21:32 ` Stephen Boyd
2015-01-30 21:25 ` [PATCH 3/3] clk: remove clk-private.h Michael Turquette
2015-01-30 23:48 ` Stephen Boyd [this message]
2015-01-31 1:18 ` Mike Turquette
2015-02-02 14:01 ` Geert Uytterhoeven
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=54CC185E.9010007@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@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