From: Amelie Delaunay <amelie.delaunay@foss.st.com>
To: Alexey Khoroshilov <khoroshilov@ispras.ru>,
Vinod Koul <vkoul@kernel.org>,
Amelie Delaunay <amelie.delaunay@st.com>
Cc: <dmaengine@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-kernel@vger.kernel.org>, <ldv-project@linuxtesting.org>
Subject: Re: [PATCH] dmaengine: stm32-mdma: Remove dead code in stm32_mdma_irq_handler()
Date: Wed, 15 Jun 2022 16:42:34 +0200 [thread overview]
Message-ID: <6e1f0081-5f1c-4865-cb66-dd2cf9a5c868@foss.st.com> (raw)
In-Reply-To: <1655072638-9103-1-git-send-email-khoroshilov@ispras.ru>
Hi Alexey,
On 6/13/22 00:23, Alexey Khoroshilov wrote:
> Local variable chan is initialized by an address of element of chan array
> that is part of stm32_mdma_device struct, so it does not make sense to
> compare chan with NULL.
>
> Found by Linux Verification Center (linuxtesting.org) with SVACE.
>
> Signed-off-by: Alexey Khoroshilov <khoroshilov@ispras.ru>
> Fixes: a4ffb13c8946 ("dmaengine: Add STM32 MDMA driver")
> ---
> drivers/dma/stm32-mdma.c | 5 -----
> 1 file changed, 5 deletions(-)
>
> diff --git a/drivers/dma/stm32-mdma.c b/drivers/dma/stm32-mdma.c
> index caf0cce8f528..b11927ed4367 100644
> --- a/drivers/dma/stm32-mdma.c
> +++ b/drivers/dma/stm32-mdma.c
> @@ -1328,12 +1328,7 @@ static irqreturn_t stm32_mdma_irq_handler(int irq, void *devid)
> return IRQ_NONE;
> }
> id = __ffs(status);
> -
> chan = &dmadev->chan[id];
> - if (!chan) {
> - dev_warn(mdma2dev(dmadev), "MDMA channel not initialized\n");
> - return IRQ_NONE;
> - }
>
> /* Handle interrupt for the channel */
> spin_lock(&chan->vchan.lock);
Thanks for your patch,
Reviewed-by: Amelie Delaunay <amelie.delaunay@foss.st.com>
next prev parent reply other threads:[~2022-06-15 14:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-12 22:23 Alexey Khoroshilov
2022-06-15 14:42 ` Amelie Delaunay [this message]
2022-06-16 16:04 ` 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=6e1f0081-5f1c-4865-cb66-dd2cf9a5c868@foss.st.com \
--to=amelie.delaunay@foss.st.com \
--cc=amelie.delaunay@st.com \
--cc=dmaengine@vger.kernel.org \
--cc=khoroshilov@ispras.ru \
--cc=ldv-project@linuxtesting.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.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
all inboxes | Powered by JetHome®