From: Stephen Boyd <sboyd@kernel.org>
To: Matthias Brugger <matthias.bgg@gmail.com>,
Michael Turquette <mturquette@baylibre.com>,
Miles Chen <miles.chen@mediatek.com>
Cc: Wendell Lin <wendell.lin@mediatek.com>,
Hanks Chen <hanks.chen@mediatek.com>,
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,
Miles Chen <miles.chen@mediatek.com>,
Lee Jones <lee.jones@linaro.org>
Subject: Re: [PATCH v3 1/3] clk: composite: export clk_register_composite
Date: Tue, 14 Sep 2021 18:23:43 -0700 [thread overview]
Message-ID: <163166902348.763609.9050267699584062754@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <20210901222526.31065-2-miles.chen@mediatek.com>
Quoting Miles Chen (2021-09-01 15:25:24)
> To support module build of mediatek clk drivers,
> it is necessary to export clk_register_composite.
>
> Cc: Stephen Boyd <sboyd@kernel.org>
> Cc: Hanks Chen <hanks.chen@mediatek.com>
> Cc: Wendell Lin <wendell.lin@mediatek.com>
> Cc: Lee Jones <lee.jones@linaro.org>
> Signed-off-by: Miles Chen <miles.chen@mediatek.com>
> ---
Applied to clk-next
next prev parent reply other threads:[~2021-09-15 1:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-01 22:25 [PATCH v3 0/4] clk: mediatek: modularize COMMON_CLK_MT6779 Miles Chen
2021-09-01 22:25 ` [PATCH v3 1/3] clk: composite: export clk_register_composite Miles Chen
2021-09-15 1:23 ` Stephen Boyd [this message]
2021-09-01 22:25 ` [PATCH v3 2/3] clk: mediatek: support COMMON_CLK_MEDIATEK module build Miles Chen
2021-09-15 1:23 ` Stephen Boyd
2021-09-01 22:25 ` [PATCH v3 3/3] clk: mediatek: support COMMON_CLK_MT6779 " Miles Chen
2021-09-15 1:23 ` Stephen Boyd
2021-09-15 1:23 ` [PATCH v3 0/4] clk: mediatek: modularize COMMON_CLK_MT6779 Stephen Boyd
2021-09-15 1:49 ` Miles Chen
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=163166902348.763609.9050267699584062754@swboyd.mtv.corp.google.com \
--to=sboyd@kernel.org \
--cc=hanks.chen@mediatek.com \
--cc=lee.jones@linaro.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=miles.chen@mediatek.com \
--cc=mturquette@baylibre.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).