From: Michael Ellerman <mpe@ellerman.id.au>
To: Julian Margetson <runaway@candw.ms>
Cc: tj@kernel.org, andriy.shevchenko@linux.intel.com,
linuxppc-dev@lists.ozlabs.org, Ian Munsie <imunsie@au1.ibm.com>
Subject: Re: Kernel 4.1-rc1 build fails on Sam460ex amcc 460ex powerpc Canyonlands
Date: Tue, 28 Apr 2015 11:12:25 +1000 [thread overview]
Message-ID: <1430183545.7246.1.camel@ellerman.id.au> (raw)
In-Reply-To: <553E16A0.704@candw.ms>
On Mon, 2015-04-27 at 06:59 -0400, Julian Margetson wrote:
> Kernel 4.1-rc1 build fails on Sam460ex amcc 460ex powerpc Canyonlands with
> CONFIG_SATA_DWC=y
>
> sata_dwc_460ex.c:(.text+0xa165c): undefined reference to `dw_dma_remove'
> drivers/built-in.o: In function `sata_dwc_probe':
> sata_dwc_460ex.c:(.text+0xa1900): undefined reference to `dw_dma_probe'
> sata_dwc_460ex.c:(.text+0xa1954): undefined reference to `dw_dma_remove'
> make: *** [vmlinux] Error 1
Looks like it was caused by:
commit 8b3444852a2b58129ee68a8dd69fef81ceb902a1
Author: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Date: Tue Mar 3 22:41:21 2015 +0200
sata_dwc_460ex: move to generic DMA driver
The SATA implementation based on two actually different devices, i.e. SATA and
DMA controllers.
For Synopsys DesignWare DMA we have already a generic implementation of the
driver. Thus, the patch converts the code to use DMAEngine framework and
dw_dmac driver.
In future it will be better to split the devices inside DTS as well like it's
done on other platforms.
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Signed-off-by: Tejun Heo <tj@kernel.org>
cheers
next prev parent reply other threads:[~2015-04-28 1:12 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-15 12:16 Problems with Kernels 3.17-rc1 and onwards on Acube Sam460 AMCC 460ex board Julian Margetson
2015-02-16 0:18 ` Michael Ellerman
2015-02-18 19:45 ` Julian Margetson
2015-02-19 0:13 ` Michael Ellerman
2015-02-19 1:36 ` Julian Margetson
2015-02-19 2:56 ` Michael Ellerman
2015-02-19 3:25 ` Julian Margetson
2015-02-20 19:25 ` Julian Margetson
2015-02-24 0:32 ` Michael Ellerman
2015-02-24 2:22 ` Julian Margetson
2015-02-24 11:08 ` Julian Margetson
2015-02-24 19:14 ` Gerhard Pircher
2015-02-24 20:26 ` Julian Margetson
2015-02-25 13:26 ` Julian Margetson
2015-02-25 13:32 ` Julian Margetson
2015-03-04 11:46 ` Julian Margetson
2015-03-04 23:52 ` Michael Ellerman
2015-03-05 11:15 ` Julian Margetson
2015-03-07 16:10 ` Julian Margetson
2015-03-10 0:30 ` Michael Ellerman
2015-03-10 0:53 ` Julian Margetson
[not found] ` <45dfe4c8990.73f22654@smtp.gmail.com>
2015-02-24 19:05 ` Julian Margetson
2015-02-19 15:57 ` Julian Margetson
[not found] ` <54EB253F.9020704@candw.ms>
2015-02-23 15:07 ` Problems with DRI " Julian Margetson
2016-02-02 13:54 ` commit 9178ba294b6839eeff1a91bed95515d783f3ee6c Julian Margetson
2016-08-05 11:26 ` Problems with Kernels 3.17-rc1 and onwards on Acube Sam460 AMCC 460ex board Julian Margetson
2015-02-19 2:20 ` Julian Margetson
2015-02-18 20:13 ` Julian Margetson
2015-04-27 10:59 ` Kernel 4.1-rc1 build fails on Sam460ex amcc 460ex powerpc Canyonlands Julian Margetson
2015-04-28 1:12 ` Michael Ellerman [this message]
2015-04-28 3:49 ` Tejun Heo
2015-05-04 17:18 ` Andy Shevchenko
2015-05-04 18:13 ` Tejun Heo
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=1430183545.7246.1.camel@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=andriy.shevchenko@linux.intel.com \
--cc=imunsie@au1.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=runaway@candw.ms \
--cc=tj@kernel.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;
as well as URLs for NNTP newsgroup(s).