[<prev] [next>] [day] [month] [year] [list]
Message-Id: <20220422021246.2731824-1-lv.ruyi@zte.com.cn>
Date: Fri, 22 Apr 2022 02:12:46 +0000
From: cgel.zte@...il.com
To: hverkuil-cisco@...all.nl
Cc: cgel.zte@...il.com, eagle.zhou@....com,
linux-kernel@...r.kernel.org, linux-media@...r.kernel.org,
lv.ruyi@....com.cn, mchehab@...nel.org, ming.qian@....com,
shijie.qin@....com, Zeal Robot <zealci@....com.cn>
Subject: [PATCH v2] media: amphion: no need to check return value of debugfs_create functions
From: Lv Ruyi <lv.ruyi@....com.cn>
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.
Reported-by: Zeal Robot <zealci@....com.cn>
Signed-off-by: Lv Ruyi <lv.ruyi@....com.cn>
---
v2: remove all the debugfs checks
---
drivers/media/platform/amphion/vpu_dbg.c | 12 ------------
1 file changed, 12 deletions(-)
diff --git a/drivers/media/platform/amphion/vpu_dbg.c b/drivers/media/platform/amphion/vpu_dbg.c
index 376196bea178..da62bd718fb8 100644
--- a/drivers/media/platform/amphion/vpu_dbg.c
+++ b/drivers/media/platform/amphion/vpu_dbg.c
@@ -413,10 +413,6 @@ int vpu_inst_create_dbgfs_file(struct vpu_inst *inst)
vpu->debugfs,
inst,
&vpu_dbg_inst_fops);
- if (!inst->debugfs) {
- dev_err(inst->dev, "vpu create debugfs %s fail\n", name);
- return -EINVAL;
- }
return 0;
}
@@ -451,10 +447,6 @@ int vpu_core_create_dbgfs_file(struct vpu_core *core)
vpu->debugfs,
core,
&vpu_dbg_core_fops);
- if (!core->debugfs) {
- dev_err(core->dev, "vpu create debugfs %s fail\n", name);
- return -EINVAL;
- }
}
if (!core->debugfs_fwlog) {
scnprintf(name, sizeof(name), "fwlog.%d", core->id);
@@ -463,10 +455,6 @@ int vpu_core_create_dbgfs_file(struct vpu_core *core)
vpu->debugfs,
core,
&vpu_dbg_fwlog_fops);
- if (!core->debugfs_fwlog) {
- dev_err(core->dev, "vpu create debugfs %s fail\n", name);
- return -EINVAL;
- }
}
return 0;
--
2.25.1
Powered by blists - more mailing lists