linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: Christoph Hellwig <hch@infradead.org>,
	David Woodhouse <dwmw2@infradead.org>,
	Lu Baolu <baolu.lu@linux.intel.com>,
	Joerg Roedel <joro@8bytes.org>, Tom Murphy <murphyt7@tcd.ie>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
	Will Deacon <will@kernel.org>,
	Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
	linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
	Ashok Raj <ashok.raj@intel.com>
Subject: Re: [PATCH v6 0/7] Convert the intel iommu driver to the dma-iommu api
Date: Wed, 25 Nov 2020 14:05:17 +0000	[thread overview]
Message-ID: <160630583051.4094327.7513344162564263042.b4-ty@kernel.org> (raw)
In-Reply-To: <20201124082057.2614359-1-baolu.lu@linux.intel.com>

On Tue, 24 Nov 2020 16:20:50 +0800, Lu Baolu wrote:
> The v5 of this series could be found here.
> 
> https://lore.kernel.org/linux-iommu/20201120101719.3172693-1-baolu.lu@linux.intel.com/
> 
> Changes in this version:
> - Rebase the series to the latest iommu/next branch.
>   https://lore.kernel.org/linux-iommu/20201123100816.GA26619@infradead.org/
> 
> [...]

Applied to arm64 (for-next/iommu/vt-d), thanks!

[1/7] iommu: Handle freelists when using deferred flushing in iommu drivers
      https://git.kernel.org/arm64/c/2a2b8eaa5b25
[2/7] iommu: Add iommu_dma_free_cpu_cached_iovas()
      https://git.kernel.org/arm64/c/230309d08b87
[3/7] iommu: Allow the dma-iommu api to use bounce buffers
      https://git.kernel.org/arm64/c/82612d66d51d
[4/7] iommu: Add quirk for Intel graphic devices in map_sg
      https://git.kernel.org/arm64/c/65f746e8285f
[5/7] iommu/vt-d: Update domain geometry in iommu_ops.at(de)tach_dev
      https://git.kernel.org/arm64/c/c062db039f40
[6/7] iommu/vt-d: Convert intel iommu driver to the iommu ops
      https://git.kernel.org/arm64/c/c588072bba6b
[7/7] iommu/vt-d: Cleanup after converting to dma-iommu ops
      https://git.kernel.org/arm64/c/58a8bb39490d

Cheers,
-- 
Will

https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev

      parent reply	other threads:[~2020-11-25 14:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-24  8:20 [PATCH v6 0/7] Convert the intel iommu driver to the dma-iommu api Lu Baolu
2020-11-24  8:20 ` [PATCH v6 1/7] iommu: Handle freelists when using deferred flushing in iommu drivers Lu Baolu
2020-11-24  8:20 ` [PATCH v6 2/7] iommu: Add iommu_dma_free_cpu_cached_iovas() Lu Baolu
2020-11-24  8:20 ` [PATCH v6 3/7] iommu: Allow the dma-iommu api to use bounce buffers Lu Baolu
2020-11-24  8:20 ` [PATCH v6 4/7] iommu: Add quirk for Intel graphic devices in map_sg Lu Baolu
2020-11-24  8:20 ` [PATCH v6 5/7] iommu/vt-d: Update domain geometry in iommu_ops.at(de)tach_dev Lu Baolu
2020-11-24  8:20 ` [PATCH v6 6/7] iommu/vt-d: Convert intel iommu driver to the iommu ops Lu Baolu
2020-11-24  8:20 ` [PATCH v6 7/7] iommu/vt-d: Cleanup after converting to dma-iommu ops Lu Baolu
2020-11-25 14:05 ` Will Deacon [this message]

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=160630583051.4094327.7513344162564263042.b4-ty@kernel.org \
    --to=will@kernel.org \
    --cc=ashok.raj@intel.com \
    --cc=baolu.lu@linux.intel.com \
    --cc=catalin.marinas@arm.com \
    --cc=dwmw2@infradead.org \
    --cc=hch@infradead.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=joro@8bytes.org \
    --cc=kernel-team@android.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=murphyt7@tcd.ie \
    --cc=tvrtko.ursulin@linux.intel.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).