From: Chen Zhou <chenzhou10@huawei.com>
To: Peng Ma <peng.ma@nxp.com>,
"dan.j.williams@intel.com" <dan.j.williams@intel.com>,
"vkoul@kernel.org" <vkoul@kernel.org>
Cc: "dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next] dmaengine: fsl-qdma: fix duplicated argument to &&
Date: Tue, 21 Jan 2020 11:28:42 +0800 [thread overview]
Message-ID: <96b96dda-0fdc-bbc1-cdb8-b7d0f20940e7@huawei.com> (raw)
In-Reply-To: <VI1PR04MB44314C51FA4C397F352C14C8ED0D0@VI1PR04MB4431.eurprd04.prod.outlook.com>
Hi Peng,
On 2020/1/21 10:54, Peng Ma wrote:
>
>
>> -----Original Message-----
>> From: Chen Zhou <chenzhou10@huawei.com>
>> Sent: 2020年1月20日 20:59
>> To: dan.j.williams@intel.com; vkoul@kernel.org
>> Cc: Peng Ma <peng.ma@nxp.com>; Wen He <wen.he_1@nxp.com>;
>> jiaheng.fan@nxp.com; dmaengine@vger.kernel.org;
>> linux-kernel@vger.kernel.org; chenzhou10@huawei.com
>> Subject: [PATCH -next] dmaengine: fsl-qdma: fix duplicated argument to &&
>>
>> There is duplicated argument to && in function fsl_qdma_free_chan_resources,
>> which looks like a typo, pointer fsl_queue->desc_pool also needs NULL check,
>> fix it.
>> Detected with coccinelle.
>>
> What does the " coccinelle " mean here?
The scripts in kernel dir, that is coccicheck.
Thanks,
Chen Zhou
>
>> Fixes: b092529e0aa0 ("dmaengine: fsl-qdma: Add qDMA controller driver for
>> Layerscape SoCs")
>> Signed-off-by: Chen Zhou <chenzhou10@huawei.com>
>> ---
>> drivers/dma/fsl-qdma.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/dma/fsl-qdma.c b/drivers/dma/fsl-qdma.c index
>> 8979208..95cc025 100644
>> --- a/drivers/dma/fsl-qdma.c
>> +++ b/drivers/dma/fsl-qdma.c
>> @@ -304,7 +304,7 @@ static void fsl_qdma_free_chan_resources(struct
>> dma_chan *chan)
>>
>> vchan_dma_desc_free_list(&fsl_chan->vchan, &head);
>>
>> - if (!fsl_queue->comp_pool && !fsl_queue->comp_pool)
>> + if (!fsl_queue->comp_pool && !fsl_queue->desc_pool)
>> return;
>>
> Hi Chen,
>
> Thanks very much for your patch, It is really need to check comp_pool and desc_pool here.
> Reviewed-by: Peng Ma <peng.ma@nxp.com>
> Tested-by: Peng Ma <peng.ma@nxp.com>
>
> BR,
> Peng
>> list_for_each_entry_safe(comp_temp, _comp_temp,
>> --
>> 2.7.4
>
next prev parent reply other threads:[~2020-01-21 3:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 12:58 [PATCH -next] dmaengine: fsl-qdma: fix duplicated argument to && Chen Zhou
2020-01-21 2:54 ` Peng Ma
2020-01-21 3:28 ` Chen Zhou [this message]
2020-01-21 8:24 ` Vinod Koul
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=96b96dda-0fdc-bbc1-cdb8-b7d0f20940e7@huawei.com \
--to=chenzhou10@huawei.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.ma@nxp.com \
--cc=vkoul@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