Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1503710 > unrolled thread

Re: [PATCH] dmaengine: st_fdma: fix uninitialized variable access

Started byVinod Koul <vinod.koul@intel.com>
First post2016-10-19 16:40 +0200
Last post2016-10-19 16:40 +0200
Articles 1 — 1 participant

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [PATCH] dmaengine: st_fdma: fix uninitialized variable access Vinod Koul <vinod.koul@intel.com> - 2016-10-19 16:40 +0200

#1503710 — Re: [PATCH] dmaengine: st_fdma: fix uninitialized variable access

FromVinod Koul <vinod.koul@intel.com>
Date2016-10-19 16:40 +0200
SubjectRe: [PATCH] dmaengine: st_fdma: fix uninitialized variable access
Message-ID<su0ca-2v4-41@gated-at.bofh.it>
On Wed, Oct 19, 2016 at 02:09:10PM +0200, Arnd Bergmann wrote:
> The newly added st_fdma driver introduces a build warning for
> allmodconfig when we add '-Wmaybe-uninitialized':
> 
> drivers/dma/st_fdma.c: In function 'st_fdma_probe':
> drivers/dma/st_fdma.c:777:5: error: 'ret' may be used uninitialized in this function [-Werror=maybe-uninitialized]
> 
> The warning is correct, though this can't happen in practice
> as the check is redundant (we don't get to this function if
> the pointer is NULL). Even if the function were called with a
> NULL of_node, the check is not needed because of_property_read_u32
> can deal with a NULL argument by returning an error.
> 
> Removing the unnecessary code simplifies the function and avoids
> the condition that we get the warning for.

Applied, thanks

-- 
~Vinod

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web