From: joro@8bytes.org (Joerg Roedel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] IOMMU group cleanup
Date: Fri, 11 Aug 2017 17:21:25 +0200 [thread overview]
Message-ID: <20170811152124.GH30515@8bytes.org> (raw)
In-Reply-To: <cover.1500637633.git.robin.murphy@arm.com>
On Fri, Jul 21, 2017 at 01:12:34PM +0100, Robin Murphy wrote:
> Hi all,
>
> Prompted by some discussion around the questionable usefulness of
> iommu_present() for SoC topologies, I took a look at what was left to
> finish off the intention of making groups mandatory. Turns out it
> wasn't much, so here it is. As well as the general rationalisation
> aspect, between this and the probe-deferral changes in 4.12, we should
> now be able to rely on the presence of a group unambiguously indicating
> whether a given device is associated with an IOMMU or not.
>
> Robin.
>
> Robin Murphy (4):
> iommu/msm: Add iommu_group support
> iommu/tegra-smmu: Add iommu_group support
> iommu/tegra-gart: Add iommu_group support
> iommu: Finish making iommu_group support mandatory
Applied, thanks Robin.
prev parent reply other threads:[~2017-08-11 15:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-21 12:12 [PATCH 0/4] IOMMU group cleanup Robin Murphy
2017-07-21 12:12 ` [PATCH 1/4] iommu/msm: Add iommu_group support Robin Murphy
2017-07-24 7:34 ` Sricharan R
2017-07-24 9:55 ` Robin Murphy
2017-07-26 15:29 ` Sricharan R
2017-07-21 12:12 ` [PATCH 2/4] iommu/tegra-smmu: " Robin Murphy
2017-08-02 8:12 ` Mikko Perttunen
2017-07-21 12:12 ` [PATCH 3/4] iommu/tegra-gart: " Robin Murphy
2017-07-26 20:56 ` Dmitry Osipenko
2017-07-21 12:12 ` [PATCH 4/4] iommu: Finish making iommu_group support mandatory Robin Murphy
2017-07-26 11:12 ` [PATCH 0/4] IOMMU group cleanup Joerg Roedel
2017-08-11 15:21 ` 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=20170811152124.GH30515@8bytes.org \
--to=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.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).