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 2/7] drivers: clk: unexport clk_hw_register_gpio_gate()
Date: Thu, 28 Nov 2019 15:44:45 +0100 [thread overview]
Message-ID: <20191128144450.24094-2-info@metux.net> (raw)
In-Reply-To: <20191128144450.24094-1-info@metux.net>
The function clk_hw_register_gpio_gate() 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 f9f81a31984a..f457b30e4900 100644
--- a/drivers/clk/clk-gpio.c
+++ b/drivers/clk/clk-gpio.c
@@ -169,7 +169,7 @@ static struct clk_hw *clk_register_gpio(struct device *dev, const char *name,
* @gpiod: gpio descriptor to gate this clock
* @flags: clock flags
*/
-struct clk_hw *clk_hw_register_gpio_gate(struct device *dev, const char *name,
+static struct clk_hw *clk_hw_register_gpio_gate(struct device *dev, const char *name,
const char *parent_name, struct gpio_desc *gpiod,
unsigned long flags)
{
@@ -184,7 +184,6 @@ struct clk_hw *clk_hw_register_gpio_gate(struct device *dev, const char *name,
(parent_name ? &parent_name : NULL),
(parent_name ? 1 : 0), gpiod, flags, ops);
}
-EXPORT_SYMBOL_GPL(clk_hw_register_gpio_gate);
static struct clk *clk_register_gpio_gate(struct device *dev, const char *name,
const char *parent_name, struct gpio_desc *gpiod,
diff --git a/include/linux/clk-provider.h b/include/linux/clk-provider.h
index d283f9896e86..b4338b26aed7 100644
--- a/include/linux/clk-provider.h
+++ b/include/linux/clk-provider.h
@@ -773,9 +773,6 @@ struct clk_gpio {
#define to_clk_gpio(_hw) container_of(_hw, struct clk_gpio, hw)
extern const struct clk_ops clk_gpio_gate_ops;
-struct clk_hw *clk_hw_register_gpio_gate(struct device *dev, const char *name,
- const char *parent_name, struct gpio_desc *gpiod,
- unsigned long flags);
void clk_hw_unregister_gpio_gate(struct clk_hw *hw);
extern const struct clk_ops clk_gpio_mux_ops;
--
2.11.0
next prev 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 ` Enrico Weigelt, metux IT consult [this message]
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 ` [PATCH 4/7] drivers: clk: unexport clk_register_gpio_mux() Enrico Weigelt, metux IT consult
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-2-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).