From: Joerg Roedel <joro@8bytes.org>
To: John Garry <john.garry@huawei.com>
Cc: will@kernel.org, dwmw2@infradead.org, baolu.lu@linux.intel.com,
robin.murphy@arm.com, corbet@lwn.net,
linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
linuxarm@huawei.com, thunder.leizhen@huawei.com,
chenxiang66@hisilicon.com, linux-doc@vger.kernel.org,
dianders@chromium.org
Subject: Re: [PATCH v15 0/6] iommu: Enhance IOMMU default DMA mode build options
Date: Mon, 26 Jul 2021 13:28:00 +0200 [thread overview]
Message-ID: <YP6cQDSuH7toUouj@8bytes.org> (raw)
In-Reply-To: <1626088340-5838-1-git-send-email-john.garry@huawei.com>
On Mon, Jul 12, 2021 at 07:12:14PM +0800, John Garry wrote:
> John Garry (3):
> iommu: Deprecate Intel and AMD cmdline methods to enable strict mode
> iommu: Print strict or lazy mode at init time
> iommu: Remove mode argument from iommu_set_dma_strict()
>
> Zhen Lei (3):
> iommu: Enhance IOMMU default DMA mode build options
> iommu/vt-d: Add support for IOMMU default DMA mode build options
> iommu/amd: Add support for IOMMU default DMA mode build options
Applied to iommu/core, thanks.
prev parent reply other threads:[~2021-07-26 11:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-12 11:12 [PATCH v15 0/6] iommu: Enhance IOMMU default DMA mode build options John Garry
2021-07-12 11:12 ` [PATCH v15 1/6] iommu: Deprecate Intel and AMD cmdline methods to enable strict mode John Garry
2021-07-12 11:12 ` [PATCH v15 2/6] iommu: Print strict or lazy mode at init time John Garry
2021-07-12 11:12 ` [PATCH v15 3/6] iommu: Enhance IOMMU default DMA mode build options John Garry
2021-07-12 11:12 ` [PATCH v15 4/6] iommu/vt-d: Add support for " John Garry
2021-07-12 11:12 ` [PATCH v15 5/6] iommu/amd: " John Garry
2021-07-12 11:12 ` [PATCH v15 6/6] iommu: Remove mode argument from iommu_set_dma_strict() John Garry
2021-07-26 11:28 ` Joerg Roedel [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=YP6cQDSuH7toUouj@8bytes.org \
--to=joro@8bytes.org \
--cc=baolu.lu@linux.intel.com \
--cc=chenxiang66@hisilicon.com \
--cc=corbet@lwn.net \
--cc=dianders@chromium.org \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=john.garry@huawei.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=robin.murphy@arm.com \
--cc=thunder.leizhen@huawei.com \
--cc=will@kernel.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 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).