From: Hugo Villeneuve Date: Mon, 23 Mar 2026 14:03:35 +0000 (-0400) Subject: regulator: core: fix typo in comments X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=09a1361db3abfcb76d936aa76820c37e0ee36c04;p=thirdparty%2Fkernel%2Fstable.git regulator: core: fix typo in comments Replace another->other so that the sentence makes sense. Signed-off-by: Hugo Villeneuve Link: https://patch.msgid.link/20260323140340.105362-1-hugo@hugovil.com Signed-off-by: Mark Brown --- 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