History

mfd: aat2870: 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.

Greg Kroah-Hartman committed 7 years ago

Commit cbfe6121 parent 64e8a9b2 files · +2 −12Browse files

Unified · Split

2 files
  1. drivers/mfd/aat2870-core.c +2 −11
  2. include/linux/mfd/aat2870.h +0 −1
drivers/mfd/aat2870-core.c+2−11
@@ -321,18 +321,9 @@ static const struct file_operations aat2870_reg_fops = { · 320 unmodified lines
321321 static void aat2870_init_debugfs(struct aat2870_data *aat2870)
322322 {
323323 aat2870->dentry_root = debugfs_create_dir("aat2870", NULL);
324− if (!aat2870->dentry_root) {
325− dev_warn(aat2870->dev,
326− "Failed to create debugfs root directory\n");
327− return;
328− }
329324
330− aat2870->dentry_reg = debugfs_create_file("regs", 0644,
331− aat2870->dentry_root,
332− aat2870, &aat2870_reg_fops);
333− if (!aat2870->dentry_reg)
334− dev_warn(aat2870->dev,
335− "Failed to create debugfs register file\n");
325+ debugfs_create_file("regs", 0644, aat2870->dentry_root, aat2870,
326+ &aat2870_reg_fops);
336327 }
337328
338329 #else
include/linux/mfd/aat2870.h+0−1
@@ -136,7 +136,6 @@ struct aat2870_data { · 135 unmodified lines
136136
137137 /* for debugfs */
138138 struct dentry *dentry_root;
139− struct dentry *dentry_reg;
140139 };
141140
142141 struct aat2870_subdev_info {

Keyboard shortcuts

General

Show keyboard shortcuts
?
Focus the current search
/

Issues and pull requests

Open filters
f

Issues, pull requests and Inbox

Select next item
j↓
Select previous item
k↑
Open selected item
Enter
Dismiss filters or clear selection
Esc

Repository code

Go to file
t