From: Wendell Lin <wendell.lin@mediatek.com>
To: Matthias Brugger <matthias.bgg@gmail.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>
Cc: <linux-clk@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-mediatek@lists.infradead.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <wsd_upstream@mediatek.com>,
Wendell Lin <wendell.lin@mediatek.com>
Subject: [PATCH 1/1] clk: Export clk_register_composite
Date: Thu, 23 Jul 2020 16:32:06 +0800 [thread overview]
Message-ID: <1595493126-21611-1-git-send-email-wendell.lin@mediatek.com> (raw)
clk_register_composite() will be used in mediatek's
clock kernel module, so export it to GPL modules.
Signed-off-by: Wendell Lin <wendell.lin@mediatek.com>
---
drivers/clk/clk-composite.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/clk/clk-composite.c b/drivers/clk/clk-composite.c
index 7376f57..7c609c2 100644
--- a/drivers/clk/clk-composite.c
+++ b/drivers/clk/clk-composite.c
@@ -360,6 +360,7 @@ struct clk *clk_register_composite(struct device *dev, const char *name,
return ERR_CAST(hw);
return hw->clk;
}
+EXPORT_SYMBOL_GPL(clk_register_composite);
struct clk *clk_register_composite_pdata(struct device *dev, const char *name,
const struct clk_parent_data *parent_data,
--
1.7.9.5
next reply other threads:[~2020-07-23 8:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 8:32 Wendell Lin [this message]
2020-08-10 9:36 ` [PATCH 1/1] clk: Export clk_register_composite Wendell Lin
[not found] ` <CAF2Aj3hZB08d8x6XOqsP4m5fv76fWH48U95j8ugLt-YWFJ-kkA@mail.gmail.com>
[not found] ` <162276982204.1835121.10976600065855289763@swboyd.mtv.corp.google.com>
[not found] ` <20210604082427.GE2435141@dell>
[not found] ` <20210604082524.GF2435141@dell>
2021-06-04 10:22 ` Wendell Lin
2021-06-04 13:23 ` Lee Jones
2021-06-04 19:19 ` Stephen Boyd
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=1595493126-21611-1-git-send-email-wendell.lin@mediatek.com \
--to=wendell.lin@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=wsd_upstream@mediatek.com \
/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).