From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: -next build failures in k3dma.c
Date: Tue, 13 Jan 2015 14:20:31 +0100 [thread overview]
Message-ID: <2546132.YsPQSK8ktD@wuerfel> (raw)
In-Reply-To: <20150113120751.GQ4160@sirena.org.uk>
On Tuesday 13 January 2015 12:07:51 Mark Brown wrote:
> 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 *.
Incidentally, I've restarted by randconfig build testing today, will follow
up with my fix.
Arnd
next parent reply other threads:[~2015-01-13 13:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1YAwSG-0000zm-Cs@debutante>
[not found] ` <20150113120751.GQ4160@sirena.org.uk>
2015-01-13 13:20 ` Arnd Bergmann [this message]
2015-01-13 13:23 ` [PATCH] dmaengine: k3: fix duplicate function definition Arnd Bergmann
2015-01-13 14:42 ` 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=2546132.YsPQSK8ktD@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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