From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Date: Thu, 02 Aug 2018 07:15:25 +0000 Subject: Re: use the generic dma-noncoherent code for sh V3 Message-Id: <20180802071525.GA11643@lst.de> List-Id: References: <20180725094043.32443-1-hch@lst.de> <877elcrlbe.wl-ysato@users.sourceforge.jp> <20180731072413.GA22837@lst.de> <20180802020906.GK1392@brightrain.aerifal.cx> In-Reply-To: <20180802020906.GK1392@brightrain.aerifal.cx> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Rich Felker Cc: Christoph Hellwig , Yoshinori Sato , Jacopo Mondi , Thomas Petazzoni , linux-sh@vger.kernel.org, iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org On Wed, Aug 01, 2018 at 10:09:06PM -0400, Rich Felker wrote: > On Tue, Jul 31, 2018 at 09:24:13AM +0200, Christoph Hellwig wrote: > > On Tue, Jul 31, 2018 at 03:06:13PM +0900, Yoshinori Sato wrote: > > > On Wed, 25 Jul 2018 18:40:38 +0900, > > > Christoph Hellwig wrote: > > > > > > > > Hi all, > > > > > > > > can you review these patches to switch sh to use the generic > > > > dma-noncoherent code? All the requirements are in mainline already > > > > and we've switched various architectures over to it already. > > > > > > > > Changes since V2: > > > > - drop a now obsolete export > > > > > > > > Changes since V1: > > > > - fixed two stupid compile errors and verified them using a local > > > > cross toolchain instead of the 0day buildbot > > > > > > Acked-by: Yoshinori Sato > > > > Do you want to pull this in through the sh tree? If not I'd be happy > > to take it through the dma mapping tree. > > Usually I send the pull requests for sh tree, and I'm trying to figure > out which patches are okay to merge and prepare one now, but if you're > happy to take it through the dma mapping tree go ahead, and I'll focus > on other sh stuff that needs attention. I'd love to take it through the dma mapping tree and save you some work!