Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934302AbeAJP3u (ORCPT + 1 other); Wed, 10 Jan 2018 10:29:50 -0500 Received: from verein.lst.de ([213.95.11.211]:47562 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933010AbeAJP3s (ORCPT ); Wed, 10 Jan 2018 10:29:48 -0500 Date: Wed, 10 Jan 2018 16:29:45 +0100 From: Christoph Hellwig To: Robin Murphy Cc: Christoph Hellwig , iommu@lists.linux-foundation.org, linux-mips@linux-mips.org, linux-ia64@vger.kernel.org, linux-sh@vger.kernel.org, sparclinux@vger.kernel.org, Guan Xuetao , linux-arch@vger.kernel.org, linux-s390@vger.kernel.org, linux-c6x-dev@linux-c6x.org, linux-hexagon@vger.kernel.org, x86@kernel.org, Konrad Rzeszutek Wilk , linux-snps-arc@lists.infradead.org, linux-m68k@lists.linux-m68k.org, patches@groups.riscv.org, linux-metag@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Michal Simek , linux-parisc@vger.kernel.org, linux-cris-kernel@axis.com, linux-kernel@vger.kernel.org, linux-alpha@vger.kernel.org, linuxppc-dev@lists.ozlabs.org Subject: Re: [PATCH 20/33] dma-mapping: clear harmful GFP_* flags in common code Message-ID: <20180110152945.GC17790@lst.de> References: <20180110080027.13879-1-hch@lst.de> <20180110080027.13879-21-hch@lst.de> <27b90341-f9d0-356f-0194-1c7203a3f93e@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <27b90341-f9d0-356f-0194-1c7203a3f93e@arm.com> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: 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..