From: Hugo Villeneuve <hvilleneuve@dimonoff.com>

Replace another->other so that the sentence makes sense.

Signed-off-by: Hugo Villeneuve <hvilleneuve@dimonoff.com>
---
 drivers/regulator/core.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c
index 2286bdf6edcb..dc5d67767336 100644
--- a/drivers/regulator/core.c
+++ b/drivers/regulator/core.c
@@ -1550,7 +1550,7 @@ static int set_machine_constraints(struct regulator_dev *rdev,
 	 * Existing logic does not warn if over_current_protection is given as
 	 * a constraint but driver does not support that. I think we should
 	 * warn about this type of issues as it is possible someone changes
-	 * PMIC on board to another type - and the another PMIC's driver does
+	 * PMIC on board to another type - and the other PMIC's driver does
 	 * not support setting protection. Board composer may happily believe
 	 * the DT limits are respected - especially if the new PMIC HW also
 	 * supports protection but the driver does not. I won't change the logic

base-commit: c369299895a591d96745d6492d4888259b004a9e
-- 
2.47.3