From: Stephen Boyd <sboyd@kernel.org>
To: Matthias Brugger <matthias.bgg@gmail.com>,
Michael Turquette <mturquette@baylibre.com>,
Weiyi Lu <weiyi.lu@mediatek.com>,
mtk01761 <wendell.lin@mediatek.com>
Cc: linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, wsd_upstream@mediatek.com
Subject: Re: [PATCH 1/2] clk: Export clk_register_composite
Date: Fri, 10 Jul 2020 17:26:47 -0700 [thread overview]
Message-ID: <159442720733.1987609.12625915294903304595@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <1593588382-19049-2-git-send-email-wendell.lin@mediatek.com>
Quoting Wendell Lin (2020-07-01 00:26:21)
> 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..fb5cb4a 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(clk_register_composite);
Should be EXPORT_SYMBOL_GPL()
next prev parent reply other threads:[~2020-07-11 0:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 7:26 [PATCH] clk: Export clk_register_composite() for mediatek's clock kernel module Wendell Lin
2020-07-01 7:26 ` [PATCH 1/2] clk: Export clk_register_composite Wendell Lin
2020-07-11 0:26 ` Stephen Boyd [this message]
2020-07-23 8:08 ` Wendell Lin
2020-07-01 7:26 ` [PATCH 2/2] clk: mediatek: Add EXPORT_SYMBOL for kernel module support Wendell Lin
2020-07-11 16:26 ` Stephen Boyd
2020-07-23 8:09 ` Wendell Lin
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=159442720733.1987609.12625915294903304595@swboyd.mtv.corp.google.com \
--to=sboyd@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=weiyi.lu@mediatek.com \
--cc=wendell.lin@mediatek.com \
--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).