[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5757a45f-0685-a82b-edd6-ae5c98781ad3@samsung.com>
Date: Thu, 22 Dec 2022 16:34:46 +0100
From: Marek Szyprowski <m.szyprowski@...sung.com>
To: Sam Protsenko <semen.protsenko@...aro.org>,
Joerg Roedel <joro@...tes.org>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
Will Deacon <will@...nel.org>,
Robin Murphy <robin.murphy@....com>,
Janghyuck Kim <janghyuck.kim@...sung.com>,
Cho KyongHo <pullip.cho@...sung.com>,
Daniel Mentz <danielmentz@...gle.com>,
David Virag <virag.david003@...il.com>,
Sumit Semwal <sumit.semwal@...aro.org>, iommu@...ts.linux.dev,
linux-arm-kernel@...ts.infradead.org,
linux-samsung-soc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] iommu/exynos: Abstract getting the fault info
On 22.12.2022 16:23, Sam Protsenko wrote:
> On Thu, 22 Dec 2022 at 07:20, Marek Szyprowski <m.szyprowski@...sung.com> wrote:
>
> [snip]
>
>>> So, what do you think about this?
>> Okay, go ahead with your approach. If I find a better way, I will rework
>> it then. I would just like to have the code for fault handling for hw
>> v1, v5 and v7 similar as much as possible.
>>
> Thanks, Marek!
>
> Joerg, can you please apply this series? Please let me know if I need
> to rebase it first, but I guess there shouldn't be any issues, the
> SysMMU driver doesn't seem to get updated often.
Just to makes things a bit more formal - feel free to add:
Acked-by: Marek Szyprowski <m.szyprowski@...sung.com>
Best regards
--
Marek Szyprowski, PhD
Samsung R&D Institute Poland
Powered by blists - more mailing lists