summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorxiongweimin <xiongweimin@kylinos.cn>2026-07-14 10:45:08 +0800
committerWill Deacon <will@kernel.org>2026-07-22 12:27:52 +0000
commitbfc147a8d3bc74aff9f39ef64cf75dccf4f7e067 (patch)
tree256b05412a63bd3cc3aec514ee4175be1f548285
parentc579af7ec1662f20b3b1a2ec378c284463e55b43 (diff)
iommu/arm-smmu-v3: Fix grammar in comment
Correct "possibly failure" to "possibly fail". Signed-off-by: xiongweimin <xiongweimin@kylinos.cn> Signed-off-by: Will Deacon <will@kernel.org>
-rw-r--r--drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c b/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c
index a10affb483a4..023cb138a23c 100644
--- a/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c
+++ b/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c
@@ -3252,7 +3252,7 @@ static void arm_smmu_remove_master_domain(struct arm_smmu_master *master,
* 5. old domain updates its invs array, unreferencing master->build_invs
*
* For 1 and 5, prepare the two updated arrays in advance, handling any changes
- * that can possibly failure. So the actual update of either 1 or 5 won't fail.
+ * that can possibly fail. So the actual update of either 1 or 5 won't fail.
* arm_smmu_asid_lock ensures that the old invs in the domains are intact while
* we are sequencing to update them.
*/