Commit 87a9672c authored by Greg Kroah-Hartman's avatar Greg Kroah-Hartman Committed by Mauro Carvalho Chehab
Browse files

media: mtk-vpu: no need to check return value of debugfs_create functions 



When calling debugfs functions, there is no need to ever check the
return value.  The function can work or not, but the code logic should
never do something different based on this.

Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Signed-off-by: default avatarHans Verkuil <hverkuil-cisco@xs4all.nl>
Signed-off-by: default avatarMauro Carvalho Chehab <mchehab+huawei@kernel.org>
parent cb562dae

drivers/media/platform/mtk-vpu/mtk_vpu.c

+0 −5
Original line number Diff line number Diff line
@@ -849,10 +849,6 @@ static int mtk_vpu_probe(struct platform_device *pdev) 
#ifdef CONFIG_DEBUG_FS

	vpu_debugfs = debugfs_create_file("mtk_vpu", S_IRUGO, NULL, (void *)dev,

					  &vpu_debug_fops);

	if (!vpu_debugfs) {

		ret = -ENOMEM;

		goto cleanup_ipi;

	}

#endif



	/* Set PTCM to 96K and DTCM to 32K */
@@ -910,7 +906,6 @@ static int mtk_vpu_probe(struct platform_device *pdev) 
	of_reserved_mem_device_release(dev);

#ifdef CONFIG_DEBUG_FS

	debugfs_remove(vpu_debugfs);

cleanup_ipi:

#endif

	memset(vpu->ipi_desc, 0, sizeof(struct vpu_ipi_desc) * IPI_MAX);

vpu_mutex_destroy: