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.

Cc: Jesper Nilsson <[email protected]>
Cc: Lars Persson <[email protected]>
Cc: Herbert Xu <[email protected]>
Cc: "David S. Miller" <[email protected]>
Cc: [email protected]
Cc: [email protected]
Signed-off-by: Greg Kroah-Hartman <[email protected]>
---
 drivers/crypto/axis/artpec6_crypto.c | 9 ---------
 1 file changed, 9 deletions(-)

diff --git a/drivers/crypto/axis/artpec6_crypto.c 
b/drivers/crypto/axis/artpec6_crypto.c
index f3442c2bdbdc..1a1858cea979 100644
--- a/drivers/crypto/axis/artpec6_crypto.c
+++ b/drivers/crypto/axis/artpec6_crypto.c
@@ -2984,12 +2984,6 @@ static void artpec6_crypto_init_debugfs(void)
 {
        dbgfs_root = debugfs_create_dir("artpec6_crypto", NULL);
 
-       if (!dbgfs_root || IS_ERR(dbgfs_root)) {
-               dbgfs_root = NULL;
-               pr_err("%s: Could not initialise debugfs!\n", MODULE_NAME);
-               return;
-       }
-
 #ifdef CONFIG_FAULT_INJECTION
        fault_create_debugfs_attr("fail_status_read", dbgfs_root,
                                  &artpec6_crypto_fail_status_read);
@@ -3001,9 +2995,6 @@ static void artpec6_crypto_init_debugfs(void)
 
 static void artpec6_crypto_free_debugfs(void)
 {
-       if (!dbgfs_root)
-               return;
-
        debugfs_remove_recursive(dbgfs_root);
        dbgfs_root = NULL;
 }
-- 
2.20.1

Reply via email to