aboutsummaryrefslogtreecommitdiff
path: root/drivers/iio/trigger/stm32-timer-trigger.c
diff options
context:
space:
mode:
authorUwe Kleine-König <u.kleine-koenig@pengutronix.de>2023-09-19 19:49:18 +0200
committerJonathan Cameron <Jonathan.Cameron@huawei.com>2023-09-23 15:06:55 +0100
commit3e1e6787dc4b42c09a23cfe4e898b01f5a07b559 (patch)
tree9342e318e77160045b4170ed1e22f81d2848992b /drivers/iio/trigger/stm32-timer-trigger.c
parentb06ab8c8ac9da9d03cec61678fe04404450ee76a (diff)
downloadlinux-3e1e6787dc4b42c09a23cfe4e898b01f5a07b559.tar.gz
linux-3e1e6787dc4b42c09a23cfe4e898b01f5a07b559.tar.bz2
linux-3e1e6787dc4b42c09a23cfe4e898b01f5a07b559.zip
iio: light: cm3605: 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 ignored (apart from emitting a warning) 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. Eventually after all drivers are converted, .remove_new() will be renamed to .remove(). 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> Link: https://lore.kernel.org/r/20230919174931.1417681-37-u.kleine-koenig@pengutronix.de Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Diffstat (limited to 'drivers/iio/trigger/stm32-timer-trigger.c')
0 files changed, 0 insertions, 0 deletions