From: Stephen Boyd <sboyd@kernel.org>
To: Michael Tretter <m.tretter@pengutronix.de>,
linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org
Cc: kernel@pengutronix.de,
Michael Turquette <mturquette@baylibre.com>,
Michal Simek <michal.simek@xilinx.com>,
Jolly Shah <jolly.shah@xilinx.com>,
Michael Tretter <m.tretter@pengutronix.de>
Subject: Re: [PATCH v2 2/4] clk: zynqmp: do not export zynqmp_clk_register_* functions
Date: Thu, 11 Apr 2019 11:41:10 -0700 [thread overview]
Message-ID: <155500807072.20095.12736243320926102509@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <20190319100147.4178-3-m.tretter@pengutronix.de>
Quoting Michael Tretter (2019-03-19 03:01:45)
> The zynqmp_clk_register_* functions are internal functions of the
> driver. Only clkc.c uses these functions to register these clocks.
> Therefore, there is no need to export these functions.
>
> The gate and pll already don't export their register_* functions.
>
> Signed-off-by: Michael Tretter <m.tretter@pengutronix.de>
> ---
Applied to clk-next
next prev parent reply other threads:[~2019-04-11 18:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 10:01 [PATCH v2 0/4] clk: zynqmp: fix CLK_FRAC and various cleanups Michael Tretter
2019-03-19 10:01 ` [PATCH v2 1/4] clk: zynqmp: fix kerneldoc of __zynqmp_clock_get_parents Michael Tretter
2019-04-11 18:41 ` Stephen Boyd
2019-03-19 10:01 ` [PATCH v2 2/4] clk: zynqmp: do not export zynqmp_clk_register_* functions Michael Tretter
2019-04-11 18:41 ` Stephen Boyd [this message]
2019-03-19 10:01 ` [PATCH v2 3/4] clk: zynqmp: fix check for fractional clock Michael Tretter
2019-04-11 18:41 ` Stephen Boyd
2019-03-19 10:01 ` [PATCH v2 4/4] clk: zynqmp: use structs for clk query responses Michael Tretter
2019-04-04 8:16 ` [PATCH v2 0/4] clk: zynqmp: fix CLK_FRAC and various cleanups Michael Tretter
2019-04-11 18:40 ` Stephen Boyd
2019-04-12 9:36 ` Michael Tretter
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=155500807072.20095.12736243320926102509@swboyd.mtv.corp.google.com \
--to=sboyd@kernel.org \
--cc=jolly.shah@xilinx.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=m.tretter@pengutronix.de \
--cc=michal.simek@xilinx.com \
--cc=mturquette@baylibre.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).