linux-kernel - Re: m68k build failures in -next: undefined reference to `arch_dma_prep

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20190708203837.GA15713@lst.de>
Date:   Mon, 8 Jul 2019 22:38:37 +0200
From:   Christoph Hellwig <hch@....de>
To:     Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:     Christoph Hellwig <hch@....de>, Guenter Roeck <linux@...ck-us.net>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        linux-m68k <linux-m68k@...ts.linux-m68k.org>,
        Greg Ungerer <gerg@...ux-m68k.org>
Subject: Re: m68k build failures in -next: undefined reference to
 `arch_dma_prep_coherent'

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.