[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150813152040.GQ7557@n2100.arm.linux.org.uk>
Date: Thu, 13 Aug 2015 16:20:40 +0100
From: Russell King - ARM Linux <linux@....linux.org.uk>
To: Christoph Hellwig <hch@....de>
Cc: akpm@...ux-foundation.org, arnd@...db.de, catalin.marinas@....com,
will.deacon@....com, ysato@...rs.sourceforge.jp, monstr@...str.eu,
jonas@...thpole.se, cmetcalf@...hip.com, gxt@...c.pku.edu.cn,
x86@...nel.org, linux-alpha@...r.kernel.org,
linux-hexagon@...r.kernel.org, linux-ia64@...r.kernel.org,
linux-mips@...ux-mips.org, linuxppc-dev@...ts.ozlabs.org,
linux-s390@...r.kernel.org, linux-sh@...r.kernel.org,
sparclinux@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/5] dma-mapping: consolidate dma_{alloc,free}_noncoherent
On Thu, Aug 13, 2015 at 05:04:05PM +0200, Christoph Hellwig wrote:
> diff --git a/arch/arm/include/asm/dma-mapping.h b/arch/arm/include/asm/dma-mapping.h
> index 2ae3424..ab521d5 100644
> --- a/arch/arm/include/asm/dma-mapping.h
> +++ b/arch/arm/include/asm/dma-mapping.h
> @@ -175,21 +175,6 @@ static inline int dma_mapping_error(struct device *dev, dma_addr_t dma_addr)
> return dma_addr == DMA_ERROR_CODE;
> }
>
> -/*
> - * Dummy noncoherent implementation. We don't provide a dma_cache_sync
> - * function so drivers using this API are highlighted with build warnings.
> - */
I'd like a similar comment to remain after this patch explaining that we
don't support non-coherent allocations and that it'll be highlighted by
the lack of dma_cache_sync, otherwise I'm sure we'll start to get patches
to add the thing.
--
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists