All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Vinod Koul <vinod.koul@intel.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Kedareswara rao Appana <appana.durga.rao@xilinx.com>
Subject: linux-next: build warning after merge of the slave-dma tree
Date: Thu, 9 Jun 2016 11:18:30 +1000	[thread overview]
Message-ID: <20160609111830.652cb495@canb.auug.org.au> (raw)

Hi Vinod,

After merging the slave-dma tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:

drivers/dma/xilinx/xilinx_vdma.c: In function 'xilinx_dma_prep_dma_cyclic':
drivers/dma/xilinx/xilinx_vdma.c:1808:23: warning: 'segment' may be used uninitialized in this function [-Wmaybe-uninitialized]
   segment->hw.control |= XILINX_DMA_BD_SOP;

Introduced by commit

  92d794dfb699 ("dmaengine: vdma: Add support for cyclic dma mode")

I am not sure if this is tecnically a problem, but gcc certainly cannot
tell.

-- 
Cheers,
Stephen Rothwell

             reply	other threads:[~2016-06-09  1:18 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-09  1:18 Stephen Rothwell [this message]
2016-06-09  6:04 ` linux-next: build warning after merge of the slave-dma tree Appana Durga Kedareswara Rao
  -- strict thread matches above, loose matches on Subject: below --
2020-02-14  0:00 Stephen Rothwell
2020-02-14  4:41 ` Vinod Koul
2019-08-12  7:14 Stephen Rothwell
2019-08-12  9:14 ` Arnd Bergmann
2019-08-12  9:21   ` Stephen Rothwell
2018-11-26  8:09 Vinod Koul
2018-11-26  8:09 ` Vinod Koul
2018-11-26  8:09 ` Vinod Koul
2018-11-26  5:59 Stephen Rothwell
2018-09-13  2:22 Stephen Rothwell
2018-09-13  7:17 ` Angelo Dureghello
2018-07-04  3:30 Stephen Rothwell
2018-07-04  4:20 ` Vinod
2018-07-05  2:47   ` Stephen Rothwell
2018-07-05  5:01     ` Vinod
2015-03-30  6:20 Stephen Rothwell
2015-03-30  6:26 ` Appana Durga Kedareswara Rao
2015-03-30  6:26   ` Appana Durga Kedareswara Rao

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=20160609111830.652cb495@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=appana.durga.rao@xilinx.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=vinod.koul@intel.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 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.