[PATCH 09/53] drm/bridge: fsl-ldb: Convert to platform remove callback returning void

Laurent Pinchart laurent.pinchart at ideasonboard.com
Mon May 8 02:45:45 UTC 2023


Hi Uwe,

Thank you for the patch.

On Sun, May 07, 2023 at 06:25:32PM +0200, Uwe Kleine-König wrote:
> 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 at pengutronix.de>

Reviewed-by: Laurent Pinchart <laurent.pinchart at ideasonboard.com>

> ---
>  drivers/gpu/drm/bridge/fsl-ldb.c | 6 ++----
>  1 file changed, 2 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/gpu/drm/bridge/fsl-ldb.c b/drivers/gpu/drm/bridge/fsl-ldb.c
> index 6bac160b395b..450b352914f4 100644
> --- a/drivers/gpu/drm/bridge/fsl-ldb.c
> +++ b/drivers/gpu/drm/bridge/fsl-ldb.c
> @@ -347,13 +347,11 @@ static int fsl_ldb_probe(struct platform_device *pdev)
>  	return 0;
>  }
>  
> -static int fsl_ldb_remove(struct platform_device *pdev)
> +static void fsl_ldb_remove(struct platform_device *pdev)
>  {
>  	struct fsl_ldb *fsl_ldb = platform_get_drvdata(pdev);
>  
>  	drm_bridge_remove(&fsl_ldb->bridge);
> -
> -	return 0;
>  }
>  
>  static const struct of_device_id fsl_ldb_match[] = {
> @@ -367,7 +365,7 @@ MODULE_DEVICE_TABLE(of, fsl_ldb_match);
>  
>  static struct platform_driver fsl_ldb_driver = {
>  	.probe	= fsl_ldb_probe,
> -	.remove	= fsl_ldb_remove,
> +	.remove_new = fsl_ldb_remove,
>  	.driver		= {
>  		.name		= "fsl-ldb",
>  		.of_match_table	= fsl_ldb_match,
> -- 
> 2.39.2
> 

-- 
Regards,

Laurent Pinchart


More information about the dri-devel mailing list