From: Joerg Roedel <joro@8bytes.org>
To: Sam Protsenko <semen.protsenko@linaro.org>
Cc: Marek Szyprowski <m.szyprowski@samsung.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Janghyuck Kim <janghyuck.kim@samsung.com>,
Cho KyongHo <pullip.cho@samsung.com>,
Daniel Mentz <danielmentz@google.com>,
David Virag <virag.david003@gmail.com>,
Sumit Semwal <sumit.semwal@linaro.org>,
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/2] iommu/exynos: Add fault handling on SysMMU v7
Date: Wed, 25 Jan 2023 12:05:06 +0100 [thread overview]
Message-ID: <Y9EM4v0uZC9BaAm7@8bytes.org> (raw)
In-Reply-To: <20220726200739.30017-1-semen.protsenko@linaro.org>
On Tue, Jul 26, 2022 at 11:07:37PM +0300, Sam Protsenko wrote:
> Sam Protsenko (2):
> iommu/exynos: Abstract getting the fault info
> iommu/exynos: Implement fault handling on SysMMU v7
Applied, thanks.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-01-25 11:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 20:07 [PATCH 0/2] iommu/exynos: Add fault handling on SysMMU v7 Sam Protsenko
2022-07-26 20:07 ` [PATCH 1/2] iommu/exynos: Abstract getting the fault info Sam Protsenko
2022-08-12 12:25 ` Marek Szyprowski
2022-10-24 14:43 ` Sam Protsenko
2022-12-21 21:32 ` Sam Protsenko
2022-12-22 13:20 ` Marek Szyprowski
2022-12-22 15:23 ` Sam Protsenko
2022-12-22 15:34 ` Marek Szyprowski
2023-01-21 20:28 ` Sam Protsenko
2022-07-26 20:07 ` [PATCH 2/2] iommu/exynos: Implement fault handling on SysMMU v7 Sam Protsenko
2022-08-08 17:18 ` [PATCH 0/2] iommu/exynos: Add " Sam Protsenko
2023-01-25 11:05 ` 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=Y9EM4v0uZC9BaAm7@8bytes.org \
--to=joro@8bytes.org \
--cc=danielmentz@google.com \
--cc=iommu@lists.linux.dev \
--cc=janghyuck.kim@samsung.com \
--cc=krzysztof.kozlowski@linaro.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=pullip.cho@samsung.com \
--cc=robin.murphy@arm.com \
--cc=semen.protsenko@linaro.org \
--cc=sumit.semwal@linaro.org \
--cc=virag.david003@gmail.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).