From: Martin Kaiser <martin@kaiser.cx>
To: Shawn Guo <shawnguo@kernel.org>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, Martin Kaiser <martin@kaiser.cx>
Subject: [PATCH 3/3] clk: imx25: make __mx25_clocks_init return void
Date: Thu, 2 Jun 2022 10:03:44 +0200 [thread overview]
Message-ID: <20220602080344.208702-4-martin@kaiser.cx> (raw)
In-Reply-To: <20220602080344.208702-1-martin@kaiser.cx>
The __mx25_clocks_init function always returns 0 and its only
caller does not check the return value. Let's remove it.
Signed-off-by: Martin Kaiser <martin@kaiser.cx>
---
drivers/clk/imx/clk-imx25.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/clk/imx/clk-imx25.c b/drivers/clk/imx/clk-imx25.c
index 263409fca1eb..72b30dd7f05f 100644
--- a/drivers/clk/imx/clk-imx25.c
+++ b/drivers/clk/imx/clk-imx25.c
@@ -74,7 +74,7 @@ enum mx25_clks {
static struct clk *clk[clk_max];
-static int __init __mx25_clocks_init(void __iomem *ccm_base)
+static void __init __mx25_clocks_init(void __iomem *ccm_base)
{
BUG_ON(!ccm_base);
@@ -222,8 +222,6 @@ static int __init __mx25_clocks_init(void __iomem *ccm_base)
imx_register_uart_clocks(6);
imx_print_silicon_rev("i.MX25", mx25_revision());
-
- return 0;
}
static void __init mx25_clocks_init_dt(struct device_node *np)
--
2.30.2
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-06-02 8:05 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 8:03 [PATCH 0/3] ARM: imx25: print silicon revision, support 1.2 Martin Kaiser
2022-06-02 8:03 ` [PATCH 1/3] ARM: imx25: support silicon revision 1.2 Martin Kaiser
2022-06-19 3:40 ` Shawn Guo
2022-06-02 8:03 ` [PATCH 2/3] clk: imx25: print silicon revision during init Martin Kaiser
2022-06-02 8:03 ` Martin Kaiser [this message]
2022-06-23 7:51 ` [PATCH v2 0/2] ARM: imx25: print silicon revision at startup Martin Kaiser
2022-06-23 7:51 ` [PATCH v2 1/2] clk: imx25: print silicon revision during init Martin Kaiser
2022-06-23 7:51 ` [PATCH v2 2/2] clk: imx25: make __mx25_clocks_init return void Martin Kaiser
2022-07-24 17:47 ` [PATCH v3 0/2] ARM: imx25: print silicon revision at startup Martin Kaiser
2022-07-24 17:47 ` [PATCH v3 1/2] clk: imx25: print silicon revision during init Martin Kaiser
2022-07-25 10:53 ` Fabio Estevam
2022-07-24 17:47 ` [PATCH v3 2/2] clk: imx25: make __mx25_clocks_init return void Martin Kaiser
2022-07-25 10:54 ` Fabio Estevam
2022-08-15 19:07 ` [PATCH v4 0/2] ARM: imx25: print silicon revision at startup Martin Kaiser
2022-08-15 19:07 ` [PATCH v4 1/2] clk: imx25: print silicon revision during init Martin Kaiser
2022-08-15 19:07 ` [PATCH v4 2/2] clk: imx25: make __mx25_clocks_init return void Martin Kaiser
2023-05-17 15:39 ` [PATCH v5 0/2] ARM: imx25: print silicon revision at startup Martin Kaiser
2023-05-17 15:39 ` [PATCH v5 1/2] clk: imx25: print silicon revision during init Martin Kaiser
2023-05-17 15:39 ` [PATCH v5 2/2] clk: imx25: make __mx25_clocks_init return void Martin Kaiser
2023-05-17 18:21 ` [PATCH v5 0/2] ARM: imx25: print silicon revision at startup Arnd Bergmann
2023-07-30 16:39 ` [PATCH v6 " Martin Kaiser
2023-07-30 16:39 ` [PATCH v6 1/2] clk: imx25: print silicon revision during init Martin Kaiser
2023-07-30 16:39 ` [PATCH v6 2/2] clk: imx25: make __mx25_clocks_init return void Martin Kaiser
2023-08-01 19:13 ` [PATCH v6 0/2] ARM: imx25: print silicon revision at startup Stephen Boyd
2023-08-02 18:38 ` Martin Kaiser
2023-08-06 3:23 ` Shawn Guo
2023-08-07 14:38 ` Martin Kaiser
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=20220602080344.208702-4-martin@kaiser.cx \
--to=martin@kaiser.cx \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shawnguo@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).