linux-kernel - -next build failures in k3dma.c

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 13 Jan 2015 12:07:51 +0000
From:	Mark Brown <broonie@...nel.org>
To:	Maxime Ripard <maxime.ripard@...e-electrons.com>,
	Vinod Koul <vinod.koul@...el.com>
Cc:	kernel-build-reports@...ts.linaro.org,
	linaro-kernel@...ts.linaro.org, linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org
Subject: -next build failures in k3dma.c

On Tue, Jan 13, 2015 at 08:04:00AM +0000, Build bot for Mark Brown wrote:

> 	arm-allmodconfig
> ../drivers/dma/k3dma.c:823:12: error: conflicting types for 'k3_dma_resume'

For several days now k3dma.c has been failing to build in an ARM
allmodconfig because the definition of k3_dma_resume() introduced in
db08425ebd51f (dmaengine: k3: Split device_control) taking a struct
dma_chan * conflicts with that which has been in the file since it was
originally merged taking a struct device *.

Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)