From: Markus Elfring <elfr...@users.sourceforge.net>
Date: Mon, 16 Nov 2015 14:19:03 +0100

The mempool_destroy() function tests whether its argument is NULL
and then returns immediately. Thus the test around the calls is not needed.

This issue was detected by using the Coccinelle software.

Signed-off-by: Markus Elfring <elfr...@users.sourceforge.net>
---
 drivers/s390/scsi/zfcp_aux.c | 21 +++++++--------------
 1 file changed, 7 insertions(+), 14 deletions(-)

diff --git a/drivers/s390/scsi/zfcp_aux.c b/drivers/s390/scsi/zfcp_aux.c
index c00ac46..abc9c93 100644
--- a/drivers/s390/scsi/zfcp_aux.c
+++ b/drivers/s390/scsi/zfcp_aux.c
@@ -248,20 +248,13 @@ static int zfcp_allocate_low_mem_buffers(struct 
zfcp_adapter *adapter)
 
 static void zfcp_free_low_mem_buffers(struct zfcp_adapter *adapter)
 {
-       if (adapter->pool.erp_req)
-               mempool_destroy(adapter->pool.erp_req);
-       if (adapter->pool.scsi_req)
-               mempool_destroy(adapter->pool.scsi_req);
-       if (adapter->pool.scsi_abort)
-               mempool_destroy(adapter->pool.scsi_abort);
-       if (adapter->pool.qtcb_pool)
-               mempool_destroy(adapter->pool.qtcb_pool);
-       if (adapter->pool.status_read_req)
-               mempool_destroy(adapter->pool.status_read_req);
-       if (adapter->pool.sr_data)
-               mempool_destroy(adapter->pool.sr_data);
-       if (adapter->pool.gid_pn)
-               mempool_destroy(adapter->pool.gid_pn);
+       mempool_destroy(adapter->pool.erp_req);
+       mempool_destroy(adapter->pool.scsi_req);
+       mempool_destroy(adapter->pool.scsi_abort);
+       mempool_destroy(adapter->pool.qtcb_pool);
+       mempool_destroy(adapter->pool.status_read_req);
+       mempool_destroy(adapter->pool.sr_data);
+       mempool_destroy(adapter->pool.gid_pn);
 }
 
 /**
-- 
2.6.2

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to