diff options
author | Uwe Kleine-König <u.kleine-koenig@pengutronix.de> | 2023-10-15 16:59:56 +0300 |
---|---|---|
committer | Georgi Djakov <djakov@kernel.org> | 2023-10-18 13:37:39 +0300 |
commit | c8fd5a37340f9dfb02f7c340d7b602bd2f7ec449 (patch) | |
tree | c3cf8ea3f89a1be74255208a471dd0ee7726235e /drivers/md/dm-log-userspace-transfer.c | |
parent | 3642b4e5cbfe480892858f0209c6fd0a3172a103 (diff) | |
download | linux-c8fd5a37340f9dfb02f7c340d7b602bd2f7ec449.tar.xz |
interconnect: qcom: 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().
Several drivers use qcom_icc_rpmh_remove() as remove callback which
returns zero unconditionally. Make it return void and use .remove_new in
the drivers. There is no change in behaviour.
Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Reviewed-by: Konrad Dybcio <konrad.dybcio@linaro.org>
Link: https://lore.kernel.org/r/20231015135955.1537751-2-u.kleine-koenig@pengutronix.de
Signed-off-by: Georgi Djakov <djakov@kernel.org>
Diffstat (limited to 'drivers/md/dm-log-userspace-transfer.c')
0 files changed, 0 insertions, 0 deletions