kfree has taken the null pointer into account. hence it is safe
to remove the redundant null pointer check before kfree.

Signed-off-by: zhong jiang <zhongji...@huawei.com>
---
 drivers/crypto/cavium/cpt/cptvf_reqmanager.c | 20 +++++---------------
 1 file changed, 5 insertions(+), 15 deletions(-)

diff --git a/drivers/crypto/cavium/cpt/cptvf_reqmanager.c 
b/drivers/crypto/cavium/cpt/cptvf_reqmanager.c
index b0ba433..ca549c5 100644
--- a/drivers/crypto/cavium/cpt/cptvf_reqmanager.c
+++ b/drivers/crypto/cavium/cpt/cptvf_reqmanager.c
@@ -308,21 +308,11 @@ void do_request_cleanup(struct cpt_vf *cptvf,
                }
        }
 
-       if (info->scatter_components)
-               kzfree(info->scatter_components);
-
-       if (info->gather_components)
-               kzfree(info->gather_components);
-
-       if (info->out_buffer)
-               kzfree(info->out_buffer);
-
-       if (info->in_buffer)
-               kzfree(info->in_buffer);
-
-       if (info->completion_addr)
-               kzfree((void *)info->completion_addr);
-
+       kzfree(info->scatter_components);
+       kzfree(info->gather_components);
+       kzfree(info->out_buffer);
+       kzfree(info->in_buffer);
+       kzfree((void *)info->completion_addr);
        kzfree(info);
 }
 
-- 
1.7.12.4

Reply via email to