From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] dmaengine: k3: fix duplicate function definition
Date: Tue, 13 Jan 2015 20:12:57 +0530 [thread overview]
Message-ID: <20150113144257.GA3085@intel.com> (raw)
In-Reply-To: <1869934.MKKaD1UAQn@wuerfel>
On Tue, Jan 13, 2015 at 02:23:13PM +0100, Arnd Bergmann wrote:
> Commit db08425ebd51f ("dmaengine: k3: Split device_control") introduced
> two new helper functions, which unfortunately have the same names
> as the existing suspend/resume functions, resulting in a build error
> when CONFIG_PM_SLEEP is enabled:
>
> drivers/dma/k3dma.c:823:12: error: conflicting types for 'k3_dma_resume'
> static int k3_dma_resume(struct device *dev)
> ^
> drivers/dma/k3dma.c:625:12: note: previous definition of 'k3_dma_resume' was here
> static int k3_dma_resume(struct dma_chan *chan)
Applied, Thanks
--
~Vinod
WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vinod.koul@intel.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: kernel-build-reports@lists.linaro.org,
Mark Brown <broonie@kernel.org>,
Maxime Ripard <maxime.ripard@free-electrons.com>,
linaro-kernel@lists.linaro.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] dmaengine: k3: fix duplicate function definition
Date: Tue, 13 Jan 2015 20:12:57 +0530 [thread overview]
Message-ID: <20150113144257.GA3085@intel.com> (raw)
In-Reply-To: <1869934.MKKaD1UAQn@wuerfel>
On Tue, Jan 13, 2015 at 02:23:13PM +0100, Arnd Bergmann wrote:
> Commit db08425ebd51f ("dmaengine: k3: Split device_control") introduced
> two new helper functions, which unfortunately have the same names
> as the existing suspend/resume functions, resulting in a build error
> when CONFIG_PM_SLEEP is enabled:
>
> drivers/dma/k3dma.c:823:12: error: conflicting types for 'k3_dma_resume'
> static int k3_dma_resume(struct device *dev)
> ^
> drivers/dma/k3dma.c:625:12: note: previous definition of 'k3_dma_resume' was here
> static int k3_dma_resume(struct dma_chan *chan)
Applied, Thanks
--
~Vinod
next prev parent reply other threads:[~2015-01-13 14:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1YAwSG-0000zm-Cs@debutante>
2015-01-13 12:07 ` -next build failures in k3dma.c Mark Brown
2015-01-13 13:20 ` Arnd Bergmann
2015-01-13 13:20 ` Arnd Bergmann
2015-01-13 13:23 ` [PATCH] dmaengine: k3: fix duplicate function definition Arnd Bergmann
2015-01-13 13:23 ` Arnd Bergmann
2015-01-13 14:42 ` Vinod Koul [this message]
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=20150113144257.GA3085@intel.com \
--to=vinod.koul@intel.com \
--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 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.