From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Date: Mon, 30 Jul 2018 09:06:48 +0000 Subject: Re: use the generic dma-noncoherent code for sh V2 Message-Id: <20180730090648.GA18361@lst.de> List-Id: References: <20180724120147.15096-1-hch@lst.de> <20180724202115.GA4685@lst.de> <18df6608-61c1-963d-bb1a-d46320232f40@landley.net> In-Reply-To: <18df6608-61c1-963d-bb1a-d46320232f40-VoJi6FS/r0vR7s880joybQ@public.gmane.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Rob Landley Cc: Thomas Petazzoni , Rich Felker , Yoshinori Sato , linux-sh-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org, Jacopo Mondi , Christoph Hellwig On Fri, Jul 27, 2018 at 11:20:21AM -0500, Rob Landley wrote: > Speaking of DMA: Which really has nothing to do with the dma mapping code, which also means I can't help you much unfortunately. That being said sh is the last pending of the initial dma-noncoherent conversion, I'd greatly appreciate if we could get this reviewed and merge for the 4.19 merge window..