Linux-Next Archive on lore.kernel.org
 help / color / Atom feed
From: Appana Durga Kedareswara Rao <appana.durga.rao@xilinx.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Vinod Koul <vinod.koul@intel.com>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: linux-next: build warning after merge of the slave-dma tree
Date: Thu, 9 Jun 2016 06:04:03 +0000
Message-ID: <C246CAC1457055469EF09E3A7AC4E11A4A5B5325@XAP-PVEXMBX01.xlnx.xilinx.com> (raw)
In-Reply-To: <20160609111830.652cb495@canb.auug.org.au>

Hi Stephen Rothwell,


> 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;

Thanks for reporting the issue.
I have fixed it and sent the patch...

> 
> 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.

Thanks,
Kedar.

  reply index

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-09  1:18 Stephen Rothwell
2016-06-09  6:04 ` Appana Durga Kedareswara Rao [this message]
  -- 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  5:59 Stephen Rothwell
2018-11-26  8:09 ` Vinod Koul
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

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=C246CAC1457055469EF09E3A7AC4E11A4A5B5325@XAP-PVEXMBX01.xlnx.xilinx.com \
    --to=appana.durga.rao@xilinx.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --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

Linux-Next Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-next/0 linux-next/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-next linux-next/ https://lore.kernel.org/linux-next \
		linux-next@vger.kernel.org
	public-inbox-index linux-next

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-next


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git