From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Rich Felker <dalias@libc.org>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
linux-sh@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org,
Julia Lawall <julia.lawall@lip6.fr>,
David Rientjes <rientjes@google.com>
Subject: Re: [PATCH] sh-DWARF: Delete unnecessary checks before the function call "mempool_destroy"
Date: Tue, 19 Jul 2016 21:08:24 +0000 [thread overview]
Message-ID: <f02b6294-fcde-7977-b151-6e423bcce54c@users.sourceforge.net> (raw)
In-Reply-To: <564985B7.3080806@users.sourceforge.net>
> From: Markus Elfring <elfring@users.sourceforge.net>
> Date: Mon, 16 Nov 2015 08:20:36 +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 <elfring@users.sourceforge.net>
> ---
> arch/sh/kernel/dwarf.c | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/arch/sh/kernel/dwarf.c b/arch/sh/kernel/dwarf.c
> index 9d209a0..e1d751a 100644
> --- a/arch/sh/kernel/dwarf.c
> +++ b/arch/sh/kernel/dwarf.c
> @@ -1009,10 +1009,8 @@ static void __init dwarf_unwinder_cleanup(void)
> rbtree_postorder_for_each_entry_safe(cie, next_cie, &cie_root, node)
> kfree(cie);
>
> - if (dwarf_reg_pool)
> - mempool_destroy(dwarf_reg_pool);
> - if (dwarf_frame_pool)
> - mempool_destroy(dwarf_frame_pool);
> + mempool_destroy(dwarf_reg_pool);
> + mempool_destroy(dwarf_frame_pool);
> kmem_cache_destroy(dwarf_reg_cachep);
> kmem_cache_destroy(dwarf_frame_cachep);
> }
>
Would you like to integrate this update suggestion
into another source code repository?
Regards,
Markus
next prev parent reply other threads:[~2016-07-19 21:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5307CAA2.8060406@users.sourceforge.net>
[not found] ` <alpine.DEB.2.02.1402212321410.2043@localhost6.localdomain6>
[not found] ` <530A086E.8010901@users.sourceforge.net>
[not found] ` <alpine.DEB.2.02.1402231635510.1985@localhost6.localdomain6>
[not found] ` <530A72AA.3000601@users.sourceforge.net>
[not found] ` <alpine.DEB.2.02.1402240658210.2090@localhost6.localdomain6>
[not found] ` <530B5FB6.6010207@users.sourceforge.net>
[not found] ` <alpine.DEB.2.10.1402241710370.2074@hadrien>
[not found] ` <530C5E18.1020800@users.sourceforge.net>
[not found] ` <alpine.DEB.2.10.1402251014170.2080@hadrien>
[not found] ` <530CD2C4.4050903@users.sourceforge.net>
[not found] ` <alpine.DEB.2.10.1402251840450.7035@hadrien>
[not found] ` <530CF8FF.8080600@users.sourceforge.net>
[not found] ` <alpine.DEB.2.02.1402252117150.2047@localhost6.localdomain6>
[not found] ` <530DD06F.4090703@users.sourceforge.net>
[not found] ` <alpine.DEB.2.02.1402262129250.2221@localhost6.localdomain6>
[not found] ` <5317A59D.4@users.sourceforge.net>
2015-11-16 7:28 ` [PATCH] sh-DWARF: Delete unnecessary checks before the function call "mempool_destroy" SF Markus Elfring
2016-07-19 16:20 ` SF Markus Elfring
2016-07-19 19:28 ` David Rientjes
2016-07-19 21:08 ` SF Markus Elfring [this message]
2016-07-22 15:31 ` Rich Felker
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=f02b6294-fcde-7977-b151-6e423bcce54c@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=dalias@libc.org \
--cc=julia.lawall@lip6.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=rientjes@google.com \
--cc=ysato@users.sourceforge.jp \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).