From: Joerg Roedel <joro@8bytes.org>
To: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: iommu@lists.linux-foundation.org,
linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Inki Dae <inki.dae@samsung.com>, Kukjin Kim <kgene@kernel.org>,
Krzysztof Kozlowski <k.kozlowski@samsung.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Subject: Re: [PATCH v2 00/13] SYSMMU driver update and support for Exynos 5433
Date: Thu, 25 Feb 2016 15:34:03 +0100 [thread overview]
Message-ID: <20160225143403.GC16675@8bytes.org> (raw)
In-Reply-To: <1455804780-9616-1-git-send-email-m.szyprowski@samsung.com>
On Thu, Feb 18, 2016 at 03:12:47PM +0100, Marek Szyprowski wrote:
> Marek Szyprowski (13):
> iommu: exynos: rework iommu group initialization
> iommu: exynos: add support for IOMMU_DOMAIN_DMA domain type
> iommu: exynos: remove ARM-specific cache flush interface
> iommu: exynos: simplify master clock operations
> iommu: exynos: refactor code (no direct register access)
> iommu: exynos: refactor fault handling code
> iommu: exynos: refactor init config code
> iommu: exynos: unify code for fldp cache invalidation
> iommu: exynos: add support for SYSMMU controller with bogus version
> reg
> iommu: exynos: update device tree documentation
> iommu: exynos: add support for v5 SYSMMU
> iommu: exynos: add Maintainers entry for Exynos SYSMMU driver
> iommu: exynos: support multiple attach_device calls
>
> .../devicetree/bindings/iommu/samsung,sysmmu.txt | 22 +-
> MAINTAINERS | 6 +
> drivers/iommu/Kconfig | 2 +-
> drivers/iommu/exynos-iommu.c | 598 ++++++++++++---------
> 4 files changed, 372 insertions(+), 256 deletions(-)
Applied all patches and changed the subjects to:
Marek Szyprowski (13):
iommu/exynos: Rework iommu group initialization
iommu/exynos: Add support for IOMMU_DOMAIN_DMA domain type
iommu/exynos: Remove ARM-specific cache flush interface
iommu/exynos: Simplify master clock operations
iommu/exynos: Refactor code (no direct register access)
iommu/exynos: Refactor fault handling code
iommu/exynos: Refactor init config code
iommu/exynos: Unify code for fldp cache invalidation
iommu/exynos: Add support for SYSMMU controller with bogus version reg
iommu/exynos: Update device tree documentation
iommu/exynos: Add support for v5 SYSMMU
iommu/exynos: Add Maintainers entry for Exynos SYSMMU driver
iommu/exynos: Support multiple attach_device calls
Please make sure you follow this sheme for future iommu patches too.
Thanks,
Joerg
prev parent reply other threads:[~2016-02-25 14:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 14:12 [PATCH v2 00/13] SYSMMU driver update and support for Exynos 5433 Marek Szyprowski
2016-02-18 14:12 ` [PATCH v2 01/13] iommu: exynos: rework iommu group initialization Marek Szyprowski
2016-02-18 14:12 ` [PATCH v2 02/13] iommu: exynos: add support for IOMMU_DOMAIN_DMA domain type Marek Szyprowski
2016-02-18 14:12 ` [PATCH v2 03/13] iommu: exynos: remove ARM-specific cache flush interface Marek Szyprowski
2016-02-18 14:12 ` [PATCH v2 04/13] iommu: exynos: simplify master clock operations Marek Szyprowski
2016-02-18 14:12 ` [PATCH v2 05/13] iommu: exynos: refactor code (no direct register access) Marek Szyprowski
2016-02-18 14:12 ` [PATCH v2 06/13] iommu: exynos: refactor fault handling code Marek Szyprowski
2016-02-18 14:12 ` [PATCH v2 07/13] iommu: exynos: refactor init config code Marek Szyprowski
2016-02-18 14:12 ` [PATCH v2 08/13] iommu: exynos: unify code for fldp cache invalidation Marek Szyprowski
2016-02-18 14:12 ` [PATCH v2 09/13] iommu: exynos: add support for SYSMMU controller with bogus version reg Marek Szyprowski
2016-02-18 14:12 ` [PATCH v2 10/13] iommu: exynos: update device tree documentation Marek Szyprowski
2016-02-18 14:12 ` [PATCH v2 11/13] iommu: exynos: add support for v5 SYSMMU Marek Szyprowski
2016-02-18 14:12 ` [PATCH v2 12/13] iommu: exynos: add Maintainers entry for Exynos SYSMMU driver Marek Szyprowski
2016-02-18 14:13 ` [PATCH v2 13/13] iommu: exynos: support multiple attach_device calls Marek Szyprowski
2016-02-25 14:34 ` 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=20160225143403.GC16675@8bytes.org \
--to=joro@8bytes.org \
--cc=b.zolnierkie@samsung.com \
--cc=inki.dae@samsung.com \
--cc=iommu@lists.linux-foundation.org \
--cc=k.kozlowski@samsung.com \
--cc=kgene@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.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).