From: alex.williamson@redhat.com (Alex Williamson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] ipmmu-vmsa cleanup
Date: Mon, 6 Nov 2017 13:06:34 -0700 [thread overview]
Message-ID: <20171106130634.4a42e18a@t450s.home> (raw)
In-Reply-To: <cover.1507918320.git.robin.murphy@arm.com>
On Fri, 13 Oct 2017 19:23:38 +0100
Robin Murphy <robin.murphy@arm.com> wrote:
> Arnd reports a build warning[1] thanks to me missing ipmmu-vmsa's second
> set of ops when converting io-pgtable-arm users to the new iommu_iotlb_*
> callbacks. Rather than just treat the symptom with a point fix, this
> seemed like a good excuse to clean up the messy #ifdeffery and
> duplication in the driver that led to the oversight in the first place.
>
> Build-tested successfully for arm64, ARM, and ARM + CONFIG_IOMMU_DMA.
>
> Robin.
>
> [1]:https://www.mail-archive.com/linux-kernel at vger.kernel.org/msg1510423.html
>
> Robin Murphy (4):
> iommu/ipmmu-vmsa: Unify domain alloc/free
> iommu/ipmmu-vmsa: Simplify group allocation
> iommu/ipmmu-vmsa: Clean up struct ipmmu_vmsa_iommu_priv
> iommu/ipmmu-vmsa: Unify ipmmu_ops
>
> drivers/iommu/ipmmu-vmsa.c | 251 ++++++++++++++-------------------------------
> 1 file changed, 78 insertions(+), 173 deletions(-)
>
Applied to iommu/ipmmu-vmsa for v4.15. Thanks,
Alex
prev parent reply other threads:[~2017-11-06 20:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-13 18:23 [PATCH 0/4] ipmmu-vmsa cleanup Robin Murphy
2017-10-13 18:23 ` [PATCH 1/4] iommu/ipmmu-vmsa: Unify domain alloc/free Robin Murphy
2017-10-13 18:23 ` [PATCH 2/4] iommu/ipmmu-vmsa: Simplify group allocation Robin Murphy
2017-10-13 18:23 ` [PATCH 3/4] iommu/ipmmu-vmsa: Clean up struct ipmmu_vmsa_iommu_priv Robin Murphy
2017-10-13 18:23 ` [PATCH 4/4] iommu/ipmmu-vmsa: Unify ipmmu_ops Robin Murphy
2017-10-13 19:54 ` [PATCH 0/4] ipmmu-vmsa cleanup Arnd Bergmann
2017-11-06 20:06 ` Alex Williamson [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=20171106130634.4a42e18a@t450s.home \
--to=alex.williamson@redhat.com \
--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).