From: Johan Hovold Date: Wed, 22 Dec 2021 14:20:25 +0000 (+0100) Subject: media: davinci: vpif: drop probe printk X-Git-Tag: v6.1-rc5~1763^2~279 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=7e2c9c6fd89338e5d1d9677807ef4717de9f4a67;p=platform%2Fkernel%2Flinux-starfive.git media: davinci: vpif: drop probe printk Drivers should generally not print anything for a successful probe, and printing "success" before probe is done makes no sense. Drop the unnecessary and misleading dev_info() call from probe. Signed-off-by: Johan Hovold Reviewed-by: Lad Prabhakar Signed-off-by: Hans Verkuil Signed-off-by: Mauro Carvalho Chehab --- diff --git a/drivers/media/platform/davinci/vpif.c b/drivers/media/platform/davinci/vpif.c index 4a260f4..03b4e51 100644 --- a/drivers/media/platform/davinci/vpif.c +++ b/drivers/media/platform/davinci/vpif.c @@ -456,8 +456,6 @@ static int vpif_probe(struct platform_device *pdev) pm_runtime_enable(&pdev->dev); pm_runtime_get(&pdev->dev); - dev_info(&pdev->dev, "vpif probe success\n"); - /* * If VPIF Node has endpoints, assume "new" DT support, * where capture and display drivers don't have DT nodes