All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
To: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
	David Woodhouse <dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>,
	ashok.raj-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org
Subject: Re: clean up the bypass code in intel-iommu a little
Date: Thu, 11 Apr 2019 17:53:34 +0200	[thread overview]
Message-ID: <20190411155334.GC29810@8bytes.org> (raw)
In-Reply-To: <20190410161408.7119-1-hch-jcswGhMUV9g@public.gmane.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

WARNING: multiple messages have this Message-ID (diff)
From: Joerg Roedel <joro@8bytes.org>
To: Christoph Hellwig <hch@lst.de>
Cc: iommu@lists.linux-foundation.org,
	David Woodhouse <dwmw2@infradead.org>,
	ashok.raj@intel.com
Subject: Re: clean up the bypass code in intel-iommu a little
Date: Thu, 11 Apr 2019 17:53:34 +0200	[thread overview]
Message-ID: <20190411155334.GC29810@8bytes.org> (raw)
Message-ID: <20190411155334.Ce8QZE-WpCRZODe0Pgsvwu2hNGEynTNw0rqyDFWYaQ4@z> (raw)
In-Reply-To: <20190410161408.7119-1-hch@lst.de>

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
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

  parent reply	other threads:[~2019-04-11 15:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-10 16:14 clean up the bypass code in intel-iommu a little Christoph Hellwig
2019-04-10 16:14 ` Christoph Hellwig
     [not found] ` <20190410161408.7119-1-hch-jcswGhMUV9g@public.gmane.org>
2019-04-10 16:14   ` [PATCH 1/3] intel-iommu: clean up iommu_no_mapping Christoph Hellwig
2019-04-10 16:14     ` Christoph Hellwig
2019-04-10 16:14   ` [PATCH 2/3] intel-iommu: use dma_direct for bypass devices Christoph Hellwig
2019-04-10 16:14     ` Christoph Hellwig
2019-04-10 16:14   ` [PATCH 3/3] intel-iommu: don't clear GFP_DMA and GFP_DMA32 flags Christoph Hellwig
2019-04-10 16:14     ` Christoph Hellwig
2019-04-11 15:53   ` Joerg Roedel [this message]
2019-04-11 15:53     ` clean up the bypass code in intel-iommu a little Joerg Roedel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190411155334.GC29810@8bytes.org \
    --to=joro-zlv9swrftaidnm+yrofe0a@public.gmane.org \
    --cc=ashok.raj-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
    --cc=hch-jcswGhMUV9g@public.gmane.org \
    --cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.