summaryrefslogtreecommitdiffstats
path: root/drivers/dma-buf
diff options
context:
space:
mode:
authorUwe Kleine-König <u.kleine-koenig@pengutronix.de>2023-03-15 16:06:49 +0100
committerMark Brown <broonie@kernel.org>2023-03-20 13:08:46 +0000
commitacb6a6982d6b83c08014f5110b443f4e8bca459b (patch)
treef3dffe8e63cc22417caa41f849cb128befbc4c72 /drivers/dma-buf
parent15c71a4c84ba66f95c49b50fa934ab0395a1010f (diff)
downloadlinux-stable-acb6a6982d6b83c08014f5110b443f4e8bca459b.tar.gz
linux-stable-acb6a6982d6b83c08014f5110b443f4e8bca459b.tar.bz2
linux-stable-acb6a6982d6b83c08014f5110b443f4e8bca459b.zip
ASoC: pxa: pxa2xx-ac97: 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> Acked-by: Takashi Iwai <tiwai@suse.de> Acked-by: Nicolas Ferre <nicolas.ferre@microchip.com> Link: https://lore.kernel.org/r/20230315150745.67084-118-u.kleine-koenig@pengutronix.de Signed-off-by: Mark Brown <broonie@kernel.org>
Diffstat (limited to 'drivers/dma-buf')
0 files changed, 0 insertions, 0 deletions