[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190629150915.GA817@roeck-us.net>
Date: Sat, 29 Jun 2019 08:09:15 -0700
From: Guenter Roeck <linux@...ck-us.net>
To: Christoph Hellwig <hch@....de>
Cc: Vineet Gupta <vgupta@...opsys.com>,
Jonas Bonn <jonas@...thpole.se>,
Stefan Kristiansson <stefan.kristiansson@...nalahti.fi>,
Stafford Horne <shorne@...il.com>,
Helge Deller <deller@....de>,
Vladimir Murzin <vladimir.murzin@....com>,
linux-snps-arc@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org,
openrisc@...ts.librecores.org, linux-parisc@...r.kernel.org,
linux-xtensa@...ux-xtensa.org, iommu@...ts.linux-foundation.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 6/7] dma-direct: handle DMA_ATTR_NO_KERNEL_MAPPING in
common code
On Fri, Jun 14, 2019 at 04:44:30PM +0200, Christoph Hellwig wrote:
> DMA_ATTR_NO_KERNEL_MAPPING is generally implemented by allocating
> normal cacheable pages or CMA memory, and then returning the page
> pointer as the opaque handle. Lift that code from the xtensa and
> generic dma remapping implementations into the generic dma-direct
> code so that we don't even call arch_dma_alloc for these allocations.
>
> Signed-off-by: Christoph Hellwig <hch@....de>
This patch results in build failures for mips:nlm_xlp_defconfig and
mips:cavium_octeon_defconfig.
kernel/dma/direct.c:144: undefined reference to `arch_dma_prep_coherent'
Reverting the patch fixes the problem.
Guenter
Powered by blists - more mailing lists