summaryrefslogtreecommitdiffstats
path: root/drivers/thunderbolt
diff options
context:
space:
mode:
authorUwe Kleine-König <u.kleine-koenig@pengutronix.de>2023-12-26 14:28:02 +0100
committerArd Biesheuvel <ardb@kernel.org>2024-03-09 11:37:18 +0100
commit021bc4b9d7ed8dcc90dc288e59f120fa6e3087dc (patch)
tree9f14ddfc2f2269bb7648d9c96a16765d87f6eb58 /drivers/thunderbolt
parent9c55461040a9264b7e44444c53d26480b438eda6 (diff)
downloadlinux-021bc4b9d7ed8dcc90dc288e59f120fa6e3087dc.tar.gz
linux-021bc4b9d7ed8dcc90dc288e59f120fa6e3087dc.tar.bz2
linux-021bc4b9d7ed8dcc90dc288e59f120fa6e3087dc.zip
virt: efi_secret: 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> Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
Diffstat (limited to 'drivers/thunderbolt')
0 files changed, 0 insertions, 0 deletions