From: zhong jiang <zhongjiang@huawei.com>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: drm/amdgpu: remove the redundant null check
Date: Thu, 5 Sep 2019 13:48:06 +0800 [thread overview]
Message-ID: <5D70A196.3020106@huawei.com> (raw)
In-Reply-To: <62b33279-9ca9-5970-5336-a8511ce54197@web.de>
On 2019/9/5 1:50, Markus Elfring wrote:
>> debugfs_remove and kfree has taken the null check in account.
>> hence it is unnecessary to check it. Just remove the condition.
> How do you think about a wording like the following?
>
> The functions “debugfs_remove” and “kfree” tolerate the passing
> of null pointers. Hence it is unnecessary to check such arguments
> around the calls. Thus remove the extra condition check at two places.
>
It's better, Thanks
>> No functional change.
> I find this information questionable while it is partly reasonable
> according to the shown software refactoring.
>
> Can a subject like “[PATCH] drm/amdgpu: Remove two redundant
> null pointer checks” be nicer here?
>
It's more clearer, thanks, Will repost using above description in v2.
> Were any source code analysis tools involved for finding
> these update candidates?
With the help of Coccinelle. You can find out some example in scripts/coccinelle/.
Sincerely,
zhong jiang
> Regards,
> Markus
>
> .
>
next prev parent reply other threads:[~2019-09-05 5:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-03 6:15 [PATCH] drm/amdgpu: remove the redundant null check zhong jiang
2019-09-04 17:50 ` Markus Elfring
2019-09-05 5:48 ` zhong jiang [this message]
2019-09-05 8:38 ` Markus Elfring
2019-09-05 8:46 ` zhong jiang
2019-09-13 21:04 ` Alex Deucher
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=5D70A196.3020106@huawei.com \
--to=zhongjiang@huawei.com \
--cc=Markus.Elfring@web.de \
--cc=linux-kernel@vger.kernel.org \
/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