From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 09B25C433F5 for ; Sat, 19 Feb 2022 07:10:12 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 88B496B0075; Sat, 19 Feb 2022 02:10:11 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 83AE66B0078; Sat, 19 Feb 2022 02:10:11 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 72A036B0080; Sat, 19 Feb 2022 02:10:11 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (relay.hostedemail.com [64.99.140.26]) by kanga.kvack.org (Postfix) with ESMTP id 63D276B0075 for ; Sat, 19 Feb 2022 02:10:11 -0500 (EST) Received: from smtpin03.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay08.hostedemail.com (Postfix) with ESMTP id 2F5D3203FE for ; Sat, 19 Feb 2022 07:10:11 +0000 (UTC) X-FDA: 79158655422.03.25E0EA1 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by imf01.hostedemail.com (Postfix) with ESMTP id 9B0BD40003 for ; Sat, 19 Feb 2022 07:10:10 +0000 (UTC) Received: by verein.lst.de (Postfix, from userid 2407) id 008BD68D05; Sat, 19 Feb 2022 08:10:07 +0100 (CET) Date: Sat, 19 Feb 2022 08:10:07 +0100 From: Christoph Hellwig To: Baoquan He Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, akpm@linux-foundation.org, hch@lst.de, cl@linux.com, 42.hyeyoo@gmail.com, penberg@kernel.org, rientjes@google.com, iamjoonsoo.kim@lge.com, vbabka@suse.cz, David.Laight@ACULAB.COM, david@redhat.com, herbert@gondor.apana.org.au, davem@davemloft.net, linux-crypto@vger.kernel.org, steffen.klassert@secunet.com, netdev@vger.kernel.org, hca@linux.ibm.com, gor@linux.ibm.com, agordeev@linux.ibm.com, borntraeger@linux.ibm.com, svens@linux.ibm.com, linux-s390@vger.kernel.org, michael@walle.cc, linux-i2c@vger.kernel.org, wsa@kernel.org Subject: Re: [PATCH 12/22] staging: emxx_udc: Don't use GFP_DMA when calling dma_alloc_coherent() Message-ID: <20220219071007.GL26505@lst.de> References: <20220219005221.634-1-bhe@redhat.com> <20220219005221.634-13-bhe@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220219005221.634-13-bhe@redhat.com> User-Agent: Mutt/1.5.17 (2007-11-01) Authentication-Results: imf01.hostedemail.com; dkim=none; dmarc=none; spf=none (imf01.hostedemail.com: domain of hch@lst.de has no SPF policy when checking 213.95.11.211) smtp.mailfrom=hch@lst.de X-Rspam-User: X-Rspamd-Server: rspam07 X-Rspamd-Queue-Id: 9B0BD40003 X-Stat-Signature: 7xtxrr5ntchd9umm9x9b14tbu9y5y6m7 X-HE-Tag: 1645254610-626450 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000001, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Sat, Feb 19, 2022 at 08:52:11AM +0800, Baoquan He wrote: > dma_alloc_coherent() allocates dma buffer with device's addressing > limitation in mind. It's redundent to specify GFP_DMA when calling > dma_alloc_coherent(). Looks good: Reviewed-by: Christoph Hellwig