From: Joerg Roedel Subject: Re: clean up the bypass code in intel-iommu a little Date: Thu, 11 Apr 2019 17:53:34 +0200 Message-ID: <20190411155334.GC29810@8bytes.org> References: <20190410161408.7119-1-hch@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: <20190410161408.7119-1-hch-jcswGhMUV9g@public.gmane.org> 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: Christoph Hellwig Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org, David Woodhouse , ashok.raj-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org List-Id: iommu@lists.linux-foundation.org On Wed, Apr 10, 2019 at 06:14:05PM +0200, Christoph Hellwig wrote: > below are three relatively simple patches to clean up the > bypass case and make it share more code with the dma-direct > implementation. These look simple and straightforward to me, applied. Can you please also Cc LKML on iommu-patches in the future? It makes the patches easier to dig out of the email archive. Also please Cc the Intel people I added here for future intel-iommu patches (we should probably more formalize their role on the driver). Thanks, Joerg