From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH RFC] dma-direct: Try reallocation with GFP_DMA32 if possible Date: Fri, 20 Apr 2018 12:06:25 +0200 Message-ID: <20180420100625.GA6728@lst.de> References: <20180416151819.27520-1-tiwai@suse.de> <20180420094702.GA6530@lst.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: iommu-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: iommu-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: Takashi Iwai Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org, Christoph Hellwig , linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: iommu@lists.linux-foundation.org On Fri, Apr 20, 2018 at 11:58:58AM +0200, Takashi Iwai wrote: > It's because it's written on the tree with another fix patch I sent > beforehand ("[PATCH 1/2] dma-direct: Don't repeat allocation for no-op > GFP_DMA"). > > Could you check that one at first? I'm fine to rebase and resubmit > this one, if still preferred, though. That one looks fine, too. I'll add it to my patch queue.