[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Y8FSOqUqQpTa+zAU@8bytes.org>
Date: Fri, 13 Jan 2023 13:44:42 +0100
From: Joerg Roedel <joro@...tes.org>
To: Christophe JAILLET <christophe.jaillet@...adoo.fr>
Cc: Yong Wu <yong.wu@...iatek.com>, Will Deacon <will@...nel.org>,
Robin Murphy <robin.murphy@....com>,
Matthias Brugger <matthias.bgg@...il.com>,
Honghui Zhang <honghui.zhang@...iatek.com>,
linux-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org,
Joerg Roedel <jroedel@...e.de>, iommu@...ts.linux.dev,
linux-mediatek@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] iommu/mediatek-v1: Fix an error handling path in
mtk_iommu_v1_probe()
On Mon, Dec 19, 2022 at 07:06:22PM +0100, Christophe JAILLET wrote:
> Fixes: b17336c55d89 ("iommu/mediatek: add support for mtk iommu generation one HW")
> Signed-off-by: Christophe JAILLET <christophe.jaillet@...adoo.fr>
> ---
> Another option would be to use devm_clk_get_enabled(). This would save a
> few LoC in mtk_iommu_v1_hw_init() and in the remove function.
> However, it would change the order of function calls in the remove function
> so I leave it as-is.
> Let me know if it is fine and if you prefer this alternative.
> ---
> drivers/iommu/mtk_iommu_v1.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
Applied, thanks.
Powered by blists - more mailing lists