From: "Joerg Roedel (AMD)" <joro@8bytes.org>
To: markuss.broks@gmail.com
Cc: Marek Szyprowski <m.szyprowski@samsung.com>,
Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
Peter Griffin <peter.griffin@linaro.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
iommu@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] IOMMU driver improvements for modern Exynos SysMMUs
Date: Thu, 24 Sep 2026 13:18:24 +0200 [thread overview]
Message-ID: <arUG8gG8Fx3es8Hj@8bytes.org> (raw)
In-Reply-To: <20260820-exynos-iommu-fixes-v1-0-6bbcd673bb15@gmail.com>
On Thu, Aug 20, 2026 at 10:12:04PM +0300, Markuss Broks via B4 Relay wrote:
> Markuss Broks (4):
> iommu/exynos: detect SysMMUs without BLOCK mode
> iommu/exynos: fix the enable sequence for no-block SysMMUs
> iommu/exynos: fix TLB invalidation for no-block SysMMUs
> iommu/exynos: decode the v7 fault transaction info
Applied, thanks.
prev parent reply other threads:[~2026-09-24 11:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20260820191213eucas1p10a8b83c2c6ab0505f80a0b469c7ae487@eucas1p1.samsung.com>
2026-08-20 19:12 ` [PATCH 0/4] IOMMU driver improvements for modern Exynos SysMMUs Markuss Broks
2026-08-20 19:12 ` Markuss Broks via B4 Relay
2026-08-20 19:12 ` [PATCH 1/4] iommu/exynos: detect SysMMUs without BLOCK mode Markuss Broks
2026-08-20 19:12 ` Markuss Broks via B4 Relay
2026-08-20 19:12 ` [PATCH 2/4] iommu/exynos: fix the enable sequence for no-block SysMMUs Markuss Broks
2026-08-20 19:12 ` Markuss Broks via B4 Relay
2026-08-20 19:12 ` [PATCH 3/4] iommu/exynos: fix TLB invalidation " Markuss Broks
2026-08-20 19:12 ` Markuss Broks via B4 Relay
2026-08-20 19:12 ` [PATCH 4/4] iommu/exynos: decode the v7 fault transaction info Markuss Broks
2026-08-20 19:12 ` Markuss Broks via B4 Relay
2026-08-25 8:16 ` [PATCH 0/4] IOMMU driver improvements for modern Exynos SysMMUs Marek Szyprowski
2026-09-24 11:18 ` Joerg Roedel (AMD) [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=arUG8gG8Fx3es8Hj@8bytes.org \
--to=joro@8bytes.org \
--cc=alim.akhtar@samsung.com \
--cc=iommu@lists.linux.dev \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=markuss.broks@gmail.com \
--cc=peter.griffin@linaro.org \
--cc=robin.murphy@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.