From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 7522CA2C for ; Mon, 21 Nov 2022 08:39:29 +0000 (UTC) Received: by verein.lst.de (Postfix, from userid 2407) id 1F9D768AA6; Mon, 21 Nov 2022 09:39:25 +0100 (CET) Date: Mon, 21 Nov 2022 09:39:24 +0100 From: Christoph Hellwig To: Dennis Dalessandro , Mauro Carvalho Chehab , Alexandra Winter , Wenjia Zhang , Marek Szyprowski , Jaroslav Kysela , Takashi Iwai , Russell King , Robin Murphy Cc: linux-arm-kernel@lists.infradead.org, linux-rdma@vger.kernel.org, iommu@lists.linux.dev, linux-media@vger.kernel.org, netdev@vger.kernel.org, linux-s390@vger.kernel.org, alsa-devel@alsa-project.org Subject: Re: stop drivers from passing GFP_COMP to dma_alloc_coherent Message-ID: <20221121083924.GA28048@lst.de> References: <20221113163535.884299-1-hch@lst.de> Precedence: bulk X-Mailing-List: iommu@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20221113163535.884299-1-hch@lst.de> User-Agent: Mutt/1.5.17 (2007-11-01) I've picked this up in the for-next branch of the dma-mapping tree now.