From: WangBo <wdjjwb@163.com> To: linux-kernel@vger.kernel.org Cc: rmk+kernel@armlinux.org.uk, linux-arm-kernel@lists.infradead.org, wang.bo116@zte.com.cn Subject: [PATCH] ARM: dmabounce: NULL check before some freeing functions is Date: Wed, 27 Feb 2019 10:26:15 +0800 [thread overview] Message-ID: <1551234375-6223-1-git-send-email-wdjjwb@163.com> (raw) The function dma_pool_destroy(NULL) is safe, so removes NULL check before freeing the mem. This patch also fix the ifnullfree.cocci warnings. Signed-off-by: WangBo <wang.bo116@zte.com.cn> --- arch/arm/common/dmabounce.c | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/arch/arm/common/dmabounce.c b/arch/arm/common/dmabounce.c index 5ba4622..dd520a3 100644 --- a/arch/arm/common/dmabounce.c +++ b/arch/arm/common/dmabounce.c @@ -563,10 +563,8 @@ void dmabounce_unregister_dev(struct device *dev) BUG(); } - if (device_info->small.pool) - dma_pool_destroy(device_info->small.pool); - if (device_info->large.pool) - dma_pool_destroy(device_info->large.pool); + dma_pool_destroy(device_info->small.pool); + dma_pool_destroy(device_info->large.pool); #ifdef STATS if (device_info->attr_res == 0) -- 2.7.4
WARNING: multiple messages have this Message-ID (diff)
From: WangBo <wdjjwb@163.com> To: linux-kernel@vger.kernel.org Cc: rmk+kernel@armlinux.org.uk, wang.bo116@zte.com.cn, linux-arm-kernel@lists.infradead.org Subject: [PATCH] ARM: dmabounce: NULL check before some freeing functions is Date: Wed, 27 Feb 2019 10:26:15 +0800 [thread overview] Message-ID: <1551234375-6223-1-git-send-email-wdjjwb@163.com> (raw) The function dma_pool_destroy(NULL) is safe, so removes NULL check before freeing the mem. This patch also fix the ifnullfree.cocci warnings. Signed-off-by: WangBo <wang.bo116@zte.com.cn> --- arch/arm/common/dmabounce.c | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/arch/arm/common/dmabounce.c b/arch/arm/common/dmabounce.c index 5ba4622..dd520a3 100644 --- a/arch/arm/common/dmabounce.c +++ b/arch/arm/common/dmabounce.c @@ -563,10 +563,8 @@ void dmabounce_unregister_dev(struct device *dev) BUG(); } - if (device_info->small.pool) - dma_pool_destroy(device_info->small.pool); - if (device_info->large.pool) - dma_pool_destroy(device_info->large.pool); + dma_pool_destroy(device_info->small.pool); + dma_pool_destroy(device_info->large.pool); #ifdef STATS if (device_info->attr_res == 0) -- 2.7.4 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-02-27 2:26 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-02-27 2:26 WangBo [this message] 2019-02-27 2:26 ` [PATCH] ARM: dmabounce: NULL check before some freeing functions is WangBo
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=1551234375-6223-1-git-send-email-wdjjwb@163.com \ --to=wdjjwb@163.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=rmk+kernel@armlinux.org.uk \ --cc=wang.bo116@zte.com.cn \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.