[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180110152945.GC17790@lst.de>
Date: Wed, 10 Jan 2018 16:29:45 +0100
From: Christoph Hellwig <hch@....de>
To: Robin Murphy <robin.murphy@....com>
Cc: Christoph Hellwig <hch@....de>, iommu@...ts.linux-foundation.org,
linux-mips@...ux-mips.org, linux-ia64@...r.kernel.org,
linux-sh@...r.kernel.org, sparclinux@...r.kernel.org,
Guan Xuetao <gxt@...c.pku.edu.cn>, linux-arch@...r.kernel.org,
linux-s390@...r.kernel.org, linux-c6x-dev@...ux-c6x.org,
linux-hexagon@...r.kernel.org, x86@...nel.org,
Konrad Rzeszutek Wilk <konrad@...nok.org>,
linux-snps-arc@...ts.infradead.org,
linux-m68k@...ts.linux-m68k.org, patches@...ups.riscv.org,
linux-metag@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
Michal Simek <monstr@...str.eu>, linux-parisc@...r.kernel.org,
linux-cris-kernel@...s.com, linux-kernel@...r.kernel.org,
linux-alpha@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org
Subject: Re: [PATCH 20/33] dma-mapping: clear harmful GFP_* flags in common
code
On Wed, Jan 10, 2018 at 11:59:30AM +0000, Robin Murphy wrote:
> Just a note that if we're all happy to enshrine the "allocations are always
> zeroed" behaviour in the API (I am too, for the record), we should remember
> to follow up once the dust settles to update the docs and I guess just
> #define dma_zalloc_coherent dma_alloc_coherent.
And then just remove it. But yes, another item for the todo list..
Powered by blists - more mailing lists