[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <d5291beb-7384-4ee9-a7a4-8aad931d7bc8@quicinc.com>
Date: Tue, 19 Dec 2023 18:36:31 +0530
From: Bibek Kumar Patro <quic_bibekkum@...cinc.com>
To: Konrad Dybcio <konrad.dybcio@...aro.org>, <will@...nel.org>,
<robin.murphy@....com>, <joro@...tes.org>,
<dmitry.baryshkov@...aro.org>, <jsnitsel@...hat.com>,
<quic_bjorande@...cinc.com>, <mani@...nel.org>,
<quic_eberman@...cinc.com>, <robdclark@...omium.org>,
<u.kleine-koenig@...gutronix.de>, <robh@...nel.org>,
<vladimir.oltean@....com>, <quic_pkondeti@...cinc.com>,
<quic_molvera@...cinc.com>
CC: <linux-arm-msm@...r.kernel.org>, <linux-arm-kernel@...ts.infradead.org>,
<iommu@...ts.linux.dev>, <linux-kernel@...r.kernel.org>,
<qipl.kernel.upstream@...cinc.com>
Subject: Re: [PATCH v4 5/5] iommu/arm-smmu: re-enable context caching in smmu
reset operation
On 12/16/2023 5:24 AM, Konrad Dybcio wrote:
[...]
>> +
>> + arm_mmu500_reset(smmu);
> We should check the return value here, in case the function is modified
> some day in a way that makes it return something else than 0
>
Thanks for pointing this actually. I crosschecked on the
arm_mmu500_reset function behavior, looks like there's no return value
other than 0 and so the functionality won't change. I think we can
keep it as it is in this case.
Thanks,
Bibek
> LGTM otherwise!
>
> Konrad
Powered by blists - more mailing lists