linux-clk.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Enrico Weigelt, metux IT consult" <info@metux.net>
To: linux-kernel@vger.kernel.org
Cc: mturquette@baylibre.com, sboyd@kernel.org, linux-clk@vger.kernel.org
Subject: [PATCH 4/7] drivers: clk: unexport clk_register_gpio_mux()
Date: Thu, 28 Nov 2019 15:44:47 +0100	[thread overview]
Message-ID: <20191128144450.24094-4-info@metux.net> (raw)
In-Reply-To: <20191128144450.24094-1-info@metux.net>

The function clk_register_gpio_mux() doesn't seem to have any
users outside clk-gpio.c, thus unexport and make it static.

Signed-off-by: Enrico Weigelt, metux IT consult <info@metux.net>
---
 drivers/clk/clk-gpio.c       | 3 +--
 include/linux/clk-provider.h | 3 ---
 2 files changed, 1 insertion(+), 5 deletions(-)

diff --git a/drivers/clk/clk-gpio.c b/drivers/clk/clk-gpio.c
index f457b30e4900..5aa9ffe394ef 100644
--- a/drivers/clk/clk-gpio.c
+++ b/drivers/clk/clk-gpio.c
@@ -220,7 +220,7 @@ struct clk_hw *clk_hw_register_gpio_mux(struct device *dev, const char *name,
 }
 EXPORT_SYMBOL_GPL(clk_hw_register_gpio_mux);
 
-struct clk *clk_register_gpio_mux(struct device *dev, const char *name,
+static struct clk *clk_register_gpio_mux(struct device *dev, const char *name,
 		const char * const *parent_names, u8 num_parents, struct gpio_desc *gpiod,
 		unsigned long flags)
 {
@@ -232,7 +232,6 @@ struct clk *clk_register_gpio_mux(struct device *dev, const char *name,
 		return ERR_CAST(hw);
 	return hw->clk;
 }
-EXPORT_SYMBOL_GPL(clk_register_gpio_mux);
 
 static int gpio_clk_driver_probe(struct platform_device *pdev)
 {
diff --git a/include/linux/clk-provider.h b/include/linux/clk-provider.h
index 4ac2ee6655f9..054e3c128ac5 100644
--- a/include/linux/clk-provider.h
+++ b/include/linux/clk-provider.h
@@ -775,9 +775,6 @@ struct clk_gpio {
 extern const struct clk_ops clk_gpio_gate_ops;
 
 extern const struct clk_ops clk_gpio_mux_ops;
-struct clk *clk_register_gpio_mux(struct device *dev, const char *name,
-		const char * const *parent_names, u8 num_parents, struct gpio_desc *gpiod,
-		unsigned long flags);
 struct clk_hw *clk_hw_register_gpio_mux(struct device *dev, const char *name,
 		const char * const *parent_names, u8 num_parents, struct gpio_desc *gpiod,
 		unsigned long flags);
-- 
2.11.0


  parent reply	other threads:[~2019-11-28 14:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-28 14:44 [PATCH 1/7] drivers: clk: unexport clk_register_gpio_gate() Enrico Weigelt, metux IT consult
2019-11-28 14:44 ` [PATCH 2/7] drivers: clk: unexport clk_hw_register_gpio_gate() Enrico Weigelt, metux IT consult
2019-11-28 14:44 ` [PATCH 3/7] include: linux: clk-provider: remove obsolete clk_hw_unregister_gpio_gate() Enrico Weigelt, metux IT consult
2019-11-28 14:44 ` Enrico Weigelt, metux IT consult [this message]
2019-11-28 14:44 ` [PATCH 5/7] drivers: clk: unexport clk_gpio_mux_ops field Enrico Weigelt, metux IT consult
2019-11-28 14:44 ` [PATCH 6/7] drivers: clk: unexport clk_gpio_gate_ops field Enrico Weigelt, metux IT consult
2019-11-28 14:44 ` [PATCH 7/7] drivers: clk: unexport clk_hw_register_gpio_mux() Enrico Weigelt, metux IT consult
2020-01-05 20:12 ` [PATCH 1/7] drivers: clk: unexport clk_register_gpio_gate() 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=20191128144450.24094-4-info@metux.net \
    --to=info@metux.net \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@kernel.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;
as well as URLs for NNTP newsgroup(s).