summaryrefslogtreecommitdiffstats
path: root/drivers/dma-buf
diff options
context:
space:
mode:
authorUwe Kleine-König <u.kleine-koenig@pengutronix.de>2024-03-04 22:28:40 +0100
committerChanwoo Choi <cw00.choi@samsung.com>2024-05-08 16:53:08 +0200
commit177e15dfbcaa5b3944f4586e6d42e96920b81db9 (patch)
tree0a507d3d72bdcc574ced0c42d80eb9727bfb0480 /drivers/dma-buf
parentPM / devfreq: exynos-nocp: Convert to platform remove callback returning void (diff)
downloadlinux-177e15dfbcaa5b3944f4586e6d42e96920b81db9.tar.xz
linux-177e15dfbcaa5b3944f4586e6d42e96920b81db9.zip
PM / devfreq: exynos-ppmu: 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: Chanwoo Choi <cw00.choi@samsung.com>
Diffstat (limited to 'drivers/dma-buf')
0 files changed, 0 insertions, 0 deletions