Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp608427ybi; Thu, 13 Jun 2019 23:53:08 -0700 (PDT) X-Google-Smtp-Source: APXvYqyvgewOnUaREf20OKFhncOUeYpB2Q4fVCkbpm0AxxC1iSrfxq7O/T6is1/WtgszCv368QB9 X-Received: by 2002:a65:50c3:: with SMTP id s3mr1360996pgp.177.1560495188522; Thu, 13 Jun 2019 23:53:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1560495188; cv=none; d=google.com; s=arc-20160816; b=yP5tpSdo+sGJptDxl1Slyk5XaAPX0vqprQ8kBClEhY8TY91EBXKEXy4A5gm6W/1t1k SxhC1vaDCIAuWxf+kv89M9riCg+v7AwrMFebSWrRZCAqyqUMflTay/fV0p0fQ33yEgDr Tm/Jf07ep6hYF81Yrens8ozsTcenz5x+YOMjgeZJygz6oXNXE4F+8s5dJMBeyDERk2uP Z50cx/dvBd3CRbOgOEXrmTdCpC4NQdJ2o+muvX7EYs7WBkbLM8cEPnxuzwQPSkgqcU+l vlJUCSA8RJVxBA4rmjpQge1Q1pQ/GEXxY1I0qh4CWoSCPZBxfeaq2aHJXzU7tH5RcFez jdLQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=gSGjan6tX1t4uk549hZKeqVdqeNTr4hUP1wDAgTDLlg=; b=pkzo0CmW0Tj0hg95KypKlwvhb3ZzE6D3eaPynp8W30ZwR/GW2QC4B2dHi4O4hJJhEy 3SxGJS7CVFLZyiW29ZZRJWbGcERQf1My9JZXmCRMS7z4yFYDrtFiIucpEcYSrCMDWjR+ ZEcG/MTdQ/+DfaOkOrNYCMFkfZaC8yQEfAuDBiVYF4Zy0k3cMXhs2Ue17o1KX049psqv OER8JaLbRHFq80kV7t6+en1yUY2AfJfdC7tZN+pvrkYQFhS28cckBmJ9KvyINu8pB6Uc Rw00ZCFf1GCWrkzO0G9huEtfcGgfwk6mOTzJxxc1rr0bNbpcePySsH7vekb9OC3rjncu y3Fg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id g23si1539394pfi.153.2019.06.13.23.52.51; Thu, 13 Jun 2019 23:53:08 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726115AbfFNGwc (ORCPT + 99 others); Fri, 14 Jun 2019 02:52:32 -0400 Received: from verein.lst.de ([213.95.11.211]:44566 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725834AbfFNGwb (ORCPT ); Fri, 14 Jun 2019 02:52:31 -0400 Received: by newverein.lst.de (Postfix, from userid 2407) id 14D0B68B05; Fri, 14 Jun 2019 08:52:03 +0200 (CEST) Date: Fri, 14 Jun 2019 08:52:02 +0200 From: "hch@lst.de" To: "Tan, Ley Foon" Cc: "hch@lst.de" , "iommu@lists.linux-foundation.org" , "linux-kernel@vger.kernel.org" , "monstr@monstr.eu" , "linux-mips@vger.kernel.org" , "lftan.linux@gmail.com" Subject: Re: switch nios2 and microblaze to use the generic uncached segement support Message-ID: <20190614065202.GA8084@lst.de> References: <20190603065324.9724-1-hch@lst.de> <1560476434.21652.1.camel@intel.com> <20190614054418.GA6722@lst.de> <1560492659.21652.3.camel@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1560492659.21652.3.camel@intel.com> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jun 14, 2019 at 06:11:00AM +0000, Tan, Ley Foon wrote: > On Fri, 2019-06-14 at 07:44 +0200, Christoph Hellwig wrote: > > On Fri, Jun 14, 2019 at 09:40:34AM +0800, Ley Foon Tan wrote: > > > > > > Hi?Christoph > > > > > > Can this patch in?http://git.infradead.org/users/hch/dma-mapping.gi > > > t/sh > > > ortlog/refs/heads/for-next > > > > > > [PATCH 1/2] nios2: use the generic uncached segment support in dma- > > > direct > > Hi Ley Foon, > > > > I don't understand the above sentence.??Does it imply a Reviewed-by? > Sorry, typo in my previous email.? > Can't find this patch in the git link you provided (for-next branch). > Did you push the patch? No, I did not push the microblaze and nios2 patches there. The for-next patch just has the baseline, you'll need to apply the nios2 on top of that branch to test it. If it tests good and you are fine with it I'd like to apply it to that branch.