All of lore.kernel.org
 help / color / mirror / Atom feed
From: zhong jiang <zhongjiang@huawei.com>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	LKML <linux-kernel@vger.kernel.org>,
	kernel-janitors@vger.kernel.org
Subject: Re: drm/amdgpu: remove the redundant null check
Date: Thu, 5 Sep 2019 16:46:50 +0800	[thread overview]
Message-ID: <5D70CB7A.8040307@huawei.com> (raw)
In-Reply-To: <dd351754-cb3a-b19a-64e1-f2f583c2a23a@web.de>

On 2019/9/5 16:38, Markus Elfring wrote:
>>> 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/.
> Thanks for such background information.
> Was the script “ifnullfree.cocci” applied here?
Yep
> Will it be helpful to add attribution for such tools
> to any more descriptions in your patches?
Sometimes, I will add the description in my patches. Not always.

Thanks,
zhong jiang
> Regards,
> Markus
>
> .
>

WARNING: multiple messages have this Message-ID (diff)
From: zhong jiang <zhongjiang@huawei.com>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	LKML <linux-kernel@vger.kernel.org>,
	kernel-janitors@vger.kernel.org
Subject: Re: drm/amdgpu: remove the redundant null check
Date: Thu, 05 Sep 2019 08:46:50 +0000	[thread overview]
Message-ID: <5D70CB7A.8040307@huawei.com> (raw)
In-Reply-To: <dd351754-cb3a-b19a-64e1-f2f583c2a23a@web.de>

On 2019/9/5 16:38, Markus Elfring wrote:
>>> 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/.
> Thanks for such background information.
> Was the script “ifnullfree.cocci” applied here?
Yep
> Will it be helpful to add attribution for such tools
> to any more descriptions in your patches?
Sometimes, I will add the description in my patches. Not always.

Thanks,
zhong jiang
> Regards,
> Markus
>
> .
>

WARNING: multiple messages have this Message-ID (diff)
From: zhong jiang <zhongjiang@huawei.com>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: <amd-gfx@lists.freedesktop.org>,
	<dri-devel@lists.freedesktop.org>,
	LKML <linux-kernel@vger.kernel.org>,
	<kernel-janitors@vger.kernel.org>
Subject: Re: drm/amdgpu: remove the redundant null check
Date: Thu, 5 Sep 2019 16:46:50 +0800	[thread overview]
Message-ID: <5D70CB7A.8040307@huawei.com> (raw)
In-Reply-To: <dd351754-cb3a-b19a-64e1-f2f583c2a23a@web.de>

On 2019/9/5 16:38, Markus Elfring wrote:
>>> 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/.
> Thanks for such background information.
> Was the script “ifnullfree.cocci” applied here?
Yep
> Will it be helpful to add attribution for such tools
> to any more descriptions in your patches?
Sometimes, I will add the description in my patches. Not always.

Thanks,
zhong jiang
> Regards,
> Markus
>
> .
>



  reply	other threads:[~2019-09-05  8:46 UTC|newest]

Thread overview: 12+ 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-03  6:15 ` zhong jiang
2019-09-04 17:50 ` Markus Elfring
2019-09-04 17:50   ` Markus Elfring
2019-09-05  5:48   ` zhong jiang
2019-09-05  8:38     ` Markus Elfring
2019-09-05  8:38       ` Markus Elfring
2019-09-05  8:46       ` zhong jiang [this message]
2019-09-05  8:46         ` zhong jiang
2019-09-05  8:46         ` zhong jiang
2019-09-13 21:04         ` Alex Deucher
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=5D70CB7A.8040307@huawei.com \
    --to=zhongjiang@huawei.com \
    --cc=Markus.Elfring@web.de \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kernel-janitors@vger.kernel.org \
    --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 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.