History

dma-pool: 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.

Tiezhu Yang committed 6 years ago

Commit 94035ed1 parent bf6e2d51 file · +0 −3Browse files

Showing the changes to kernel (1 of 1 file). Show all

Unified · Split

kernel/dma/pool.c+0−3
@@ -38,9 +38,6 @@ static void __init dma_atomic_pool_debugfs_init(void) · 37 unmodified lines
3838 struct dentry *root;
3939
4040 root = debugfs_create_dir("dma_pools", NULL);
41− if (IS_ERR_OR_NULL(root))
42− return;
43−
4441 debugfs_create_ulong("pool_size_dma", 0400, root, &pool_size_dma);
4542 debugfs_create_ulong("pool_size_dma32", 0400, root, &pool_size_dma32);
4643 debugfs_create_ulong("pool_size_kernel", 0400, root, &pool_size_kernel);

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