From: "tip-bot2 for Uwe Kleine-König" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: u.kleine-koenig@pengutronix.de,
Daniel Lezcano <daniel.lezcano@linaro.org>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: timers/core] clocksource/drivers/timer-tegra186: Convert to platform remove callback returning void
Date: Wed, 26 Apr 2023 09:12:31 -0000 [thread overview]
Message-ID: <168250035186.404.12792243780091538646.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20230313075430.2730803-5-u.kleine-koenig@pengutronix.de>
The following commit has been merged into the timers/core branch of tip:
Commit-ID: d7b76421c03fa58d16a52eb839302f582602997a
Gitweb: https://git.kernel.org/tip/d7b76421c03fa58d16a52eb839302f582602997a
Author: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
AuthorDate: Mon, 13 Mar 2023 08:54:29 +01:00
Committer: Daniel Lezcano <daniel.lezcano@linaro.org>
CommitterDate: Mon, 24 Apr 2023 16:56:13 +02:00
clocksource/drivers/timer-tegra186: Convert to platform remove callback returning void
The .remove() callback for a platform driver returns an int which makes
many driver authors wrongly assume it's possible to do error handling by
returning an error code. However the value returned is (mostly) ignored
and this typically results in resource leaks. To improve here there is a
quest to make the remove callback return void. In the first step of this
quest all drivers are converted to .remove_new() which already returns
void.
Trivially convert this driver from always returning zero in the remove
callback to the void returning variant.
Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Link: https://lore.kernel.org/r/20230313075430.2730803-5-u.kleine-koenig@pengutronix.de
---
drivers/clocksource/timer-tegra186.c | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/clocksource/timer-tegra186.c b/drivers/clocksource/timer-tegra186.c
index ea74288..ccc762d 100644
--- a/drivers/clocksource/timer-tegra186.c
+++ b/drivers/clocksource/timer-tegra186.c
@@ -447,15 +447,13 @@ unregister_tsc:
return err;
}
-static int tegra186_timer_remove(struct platform_device *pdev)
+static void tegra186_timer_remove(struct platform_device *pdev)
{
struct tegra186_timer *tegra = platform_get_drvdata(pdev);
clocksource_unregister(&tegra->usec);
clocksource_unregister(&tegra->osc);
clocksource_unregister(&tegra->tsc);
-
- return 0;
}
static int __maybe_unused tegra186_timer_suspend(struct device *dev)
@@ -505,7 +503,7 @@ static struct platform_driver tegra186_wdt_driver = {
.of_match_table = tegra186_timer_of_match,
},
.probe = tegra186_timer_probe,
- .remove = tegra186_timer_remove,
+ .remove_new = tegra186_timer_remove,
};
module_platform_driver(tegra186_wdt_driver);
next prev parent reply other threads:[~2023-04-26 9:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 7:54 [PATCH 0/5] clocksource: " Uwe Kleine-König
2023-03-13 7:54 ` [PATCH 1/5] clocksource: sh_mtu2: Mark driver as non-removable Uwe Kleine-König
2023-04-26 9:12 ` [tip: timers/core] clocksource/drivers/sh_mtu2: " tip-bot2 for Uwe Kleine-König
2023-03-13 7:54 ` [PATCH 2/5] clocksource: timer-stm32-lp: " Uwe Kleine-König
2023-03-13 9:43 ` Uwe Kleine-König
2023-03-13 13:10 ` kernel test robot
2023-04-26 9:12 ` [tip: timers/core] clocksource/drivers/timer-stm32-lp: " tip-bot2 for Uwe Kleine-König
2023-03-13 7:54 ` [PATCH 3/5] clocksource: timer-ti-dm: Improve error message in .remove Uwe Kleine-König
2023-04-26 9:12 ` [tip: timers/core] clocksource/drivers/timer-ti-dm: " tip-bot2 for Uwe Kleine-König
2023-03-13 7:54 ` [PATCH 4/5] clocksource: timer-tegra186: Convert to platform remove callback returning void Uwe Kleine-König
2023-04-26 9:12 ` tip-bot2 for Uwe Kleine-König [this message]
2023-03-13 7:54 ` [PATCH 5/5] clocksource: timer-ti-dm: " Uwe Kleine-König
2023-04-26 9:12 ` [tip: timers/core] clocksource/drivers/timer-ti-dm: " tip-bot2 for Uwe Kleine-König
2023-04-06 13:54 ` [PATCH 0/5] clocksource: " Daniel Lezcano
2023-04-06 14:07 ` Uwe Kleine-König
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=168250035186.404.12792243780091538646.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
--cc=x86@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
all inboxes | Powered by JetHome®