Re: [PATCH v2 1/1] iommu: Clear a lot of spelling mistakes
From: Leizhen (ThunderTown) <hidden>
Date: 2021-06-09 02:10:02
Also in:
linux-arm-kernel, linux-iommu, linux-sunxi
From: Leizhen (ThunderTown) <hidden>
Date: 2021-06-09 02:10:02
Also in:
linux-arm-kernel, linux-iommu, linux-sunxi
On 2021/6/8 17:38, Will Deacon wrote:
On Mon, May 10, 2021 at 11:54:25AM +0800, Zhen Lei wrote:quoted
All spelling mistakes are in the comments, no functional change.[...]quoted
diff --git a/drivers/iommu/mtk_iommu.c b/drivers/iommu/mtk_iommu.c index e06b8a0e2b56bdd..b9e4be35c8dcad2 100644 --- a/drivers/iommu/mtk_iommu.c +++ b/drivers/iommu/mtk_iommu.c@@ -161,7 +161,7 @@ static int mtk_iommu_hw_init(const struct mtk_iommu_data *data); * The Region 'A'(I/O) can NOT be mapped by M4U; For Region 'B'/'C'/'D', the * bit32 of the CPU physical address always is needed to set, and for Region * 'E', the CPU physical address keep as is. - * Additionally, The iommu consumers always use the CPU phyiscal address. + * Additionally, The iommu consumers always use the CPU physical address.If we're fixing typos, then I think the 'T' in "The iommu" should be lowercase here.
OK, I will change it. In addition, the current linux-next has several new spelling errors.
Anyway, all the other fixes look correct to me. I'll leave it up to Joerg as to whether he wants to apply this or not, given the impact on git blame and the potential for conflicts.
Currently, there are no conflicts in linux-next.
Will .
_______________________________________________ Linux-mediatek mailing list Linux-mediatek@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-mediatek