From: Christoph Hellwig <hch@lst.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Christoph Hellwig <hch@lst.de>,
Guenter Roeck <linux@roeck-us.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-m68k <linux-m68k@lists.linux-m68k.org>,
Greg Ungerer <gerg@linux-m68k.org>
Subject: Re: m68k build failures in -next: undefined reference to `arch_dma_prep_coherent'
Date: Mon, 8 Jul 2019 22:38:37 +0200 [thread overview]
Message-ID: <20190708203837.GA15713@lst.de> (raw)
In-Reply-To: <20190708203733.GA15607@lst.de>
On Mon, Jul 08, 2019 at 10:37:33PM +0200, Christoph Hellwig wrote:
> On Mon, Jul 08, 2019 at 10:36:05PM +0200, Geert Uytterhoeven wrote:
> > Note that the build failure is more subtle: both m5307c3_defconfig and
> > m5475evb_defconfig build fine in m68k/for-linus, but fail in
> > next-20190708. So it fails when combined with other changes, going
> > in through a different tree (the DMA tree?).
>
> Yes, the dma tree adds the stub for the symbol and adds code relying
> on that.
If you give me an ack I can add the fix to the dma-mapping pull request.
next prev parent reply other threads:[~2019-07-08 20:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-08 17:06 m68k build failures in -next: undefined reference to `arch_dma_prep_coherent' Guenter Roeck
2019-07-08 19:13 ` Geert Uytterhoeven
2019-07-08 19:45 ` Guenter Roeck
2019-07-08 20:19 ` Geert Uytterhoeven
2019-07-08 20:22 ` Christoph Hellwig
2019-07-08 20:36 ` Geert Uytterhoeven
2019-07-08 20:37 ` Christoph Hellwig
2019-07-08 20:38 ` Christoph Hellwig [this message]
2019-07-08 20:40 ` Geert Uytterhoeven
2019-07-08 20:42 ` Guenter Roeck
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=20190708203837.GA15713@lst.de \
--to=hch@lst.de \
--cc=geert@linux-m68k.org \
--cc=gerg@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux@roeck-us.net \
--cc=sfr@canb.auug.org.au \
/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