From: Vinod Koul <vinod.koul@intel.com>
To: Maninder Singh <shanky.cool1992@gmail.com>
Cc: dan.j.williams@intel.com, dmaengine@vger.kernel.org,
linux-kernel@vger.kernel.org,
Maninder Singh <maninder1.s@samsung.com>
Subject: Re: [PATCH 1/1] dmaengine: pl330: Initialize pl330 for pl330_prep_dma_memcpy after NULL check of pch
Date: Mon, 25 May 2015 22:39:35 +0530 [thread overview]
Message-ID: <20150525170935.GK3140@localhost> (raw)
In-Reply-To: <1432581005-2614-1-git-send-email-shanky.cool1992@gmail.com>
On Tue, May 26, 2015 at 12:40:05AM +0530, Maninder Singh wrote:
> From: Maninder Singh <maninder1.s@samsung.com>
>
> Currently pch pointer is already dereferenced before NULL check
> and thus we are getting below warning:
> warn: variable dereferenced before check 'pch'
>
> So initialize struct pl330_dmac *pl330 after NULL check
> of dma_pl330_chan *pch.
>
Applied, thanks
--
~Vinod
> Signed-off-by: Maninder Singh <maninder1.s@samsung.com>
> Reviewed-by: Vaneet Narang <v.narang@samsung.com>
> ---
> drivers/dma/pl330.c | 4 +++-
> 1 files changed, 3 insertions(+), 1 deletions(-)
> diff --git a/drivers/dma/pl330.c b/drivers/dma/pl330.c
> index a7d9d30..7e27144 100644
> --- a/drivers/dma/pl330.c
> +++ b/drivers/dma/pl330.c
> @@ -2581,12 +2581,14 @@ pl330_prep_dma_memcpy(struct dma_chan *chan, dma_addr_t dst,
> {
> struct dma_pl330_desc *desc;
> struct dma_pl330_chan *pch = to_pchan(chan);
> - struct pl330_dmac *pl330 = pch->dmac;
> + struct pl330_dmac *pl330;
> int burst;
>
> if (unlikely(!pch || !len))
> return NULL;
>
> + pl330 = pch->dmac;
> +
> desc = __pl330_prep_dma_memcpy(pch, dst, src, len);
> if (!desc)
> return NULL;
> --
> 1.7.1
--
next prev parent reply other threads:[~2015-05-25 17:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-25 19:10 [PATCH 1/1] dmaengine: pl330: Initialize pl330 for pl330_prep_dma_memcpy after NULL check of pch Maninder Singh
2015-05-25 17:09 ` Vinod Koul [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-05-24 18:12 Maninder Singh
[not found] ` <CAPmXEtt9yR_eWYhZJzz4k=Ay9kR_emxEQCNB2GvLZLphGYv5Eg@mail.gmail.com>
2015-05-25 5:50 ` 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=20150525170935.GK3140@localhost \
--to=vinod.koul@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maninder1.s@samsung.com \
--cc=shanky.cool1992@gmail.com \
/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