public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Yang <mmyangfl@gmail.com>
To: linux-clk@vger.kernel.org
Cc: David Yang <mmyangfl@gmail.com>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: [PATCH v3 02/14] clk: hisilicon: Rename hisi_clk_unregister macro
Date: Mon, 10 Apr 2023 19:07:14 +0800	[thread overview]
Message-ID: <20230410110733.192151-3-mmyangfl@gmail.com> (raw)
In-Reply-To: <20230410110733.192151-1-mmyangfl@gmail.com>

hisi_clk_unregister is not a function corresponding to hisi_clk_register,
rename it to avoid misunderstanding.

Signed-off-by: David Yang <mmyangfl@gmail.com>
---
 drivers/clk/hisilicon/clk.h | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/drivers/clk/hisilicon/clk.h b/drivers/clk/hisilicon/clk.h
index c373d7c14ed5..cc580915d058 100644
--- a/drivers/clk/hisilicon/clk.h
+++ b/drivers/clk/hisilicon/clk.h
@@ -179,7 +179,7 @@ int hisi_clk_early_init(struct device_node *np, const struct hisi_clocks *clks);
 int hisi_clk_probe(struct platform_device *pdev);
 int hisi_clk_remove(struct platform_device *pdev);
 
-#define hisi_clk_unregister(type) \
+#define hisi_clk_unregister_fn(type) \
 static inline \
 void hisi_clk_unregister_##type(const struct hisi_##type##_clock *clks, \
 				int nums, struct hisi_clock_data *data) \
@@ -193,10 +193,10 @@ void hisi_clk_unregister_##type(const struct hisi_##type##_clock *clks, \
 	} \
 }
 
-hisi_clk_unregister(fixed_rate)
-hisi_clk_unregister(fixed_factor)
-hisi_clk_unregister(mux)
-hisi_clk_unregister(divider)
-hisi_clk_unregister(gate)
+hisi_clk_unregister_fn(fixed_rate)
+hisi_clk_unregister_fn(fixed_factor)
+hisi_clk_unregister_fn(mux)
+hisi_clk_unregister_fn(divider)
+hisi_clk_unregister_fn(gate)
 
 #endif	/* __HISI_CLK_H */
-- 
2.39.2


  parent reply	other threads:[~2023-04-10 11:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-10 11:07 [PATCH v3 00/14] clk: hisilicon: Migrate devm APIs David Yang
2023-04-10 11:07 ` [PATCH v3 01/14] clk: hisilicon: Add helper functions for platform driver David Yang
2023-04-10 11:07 ` David Yang [this message]
2023-04-10 11:07 ` [PATCH v3 03/14] clk: hisilicon: hi3516cv300: Use helper functions David Yang
2023-04-10 11:07 ` [PATCH v3 04/14] clk: hisilicon: hi3798cv200: " David Yang
2023-04-10 11:07 ` [PATCH v3 05/14] clk: hisilicon: Remove hisi_crg_funcs David Yang
2023-04-10 11:07 ` [PATCH v3 06/14] clk: hisilicon: hi3519: Use helper functions David Yang
2023-04-10 11:07 ` [PATCH v3 07/14] clk: hisilicon: hi3559a: " David Yang
2023-04-10 11:07 ` [PATCH v3 08/14] clk: hisilicon: hi3660: Convert into module David Yang
2023-04-10 11:07 ` [PATCH v3 09/14] clk: hisilicon: hi3670: " David Yang
2023-04-10 11:07 ` [PATCH v3 10/14] clk: hisilicon: hi3620: Convert into platform driver module David Yang
2023-04-10 11:07 ` [PATCH v3 11/14] clk: hisilicon: hi6220: " David Yang
2023-04-10 11:07 ` [PATCH v3 12/14] clk: hisilicon: hip04: " David Yang
2023-04-10 11:07 ` [PATCH v3 13/14] clk: hisilicon: hix5hd2: " David Yang
2023-04-10 11:07 ` [PATCH v3 14/14] clk: hisilicon: Migrate devm APIs David Yang

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=20230410110733.192151-3-mmyangfl@gmail.com \
    --to=mmyangfl@gmail.com \
    --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