]> git.ipfire.org Git - thirdparty/kernel/stable.git/commitdiff
regulator: core: fix typo in comments
authorHugo Villeneuve <hvilleneuve@dimonoff.com>
Mon, 23 Mar 2026 14:03:35 +0000 (10:03 -0400)
committerMark Brown <broonie@kernel.org>
Mon, 23 Mar 2026 16:03:25 +0000 (16:03 +0000)
Replace another->other so that the sentence makes sense.

Signed-off-by: Hugo Villeneuve <hvilleneuve@dimonoff.com>
Link: https://patch.msgid.link/20260323140340.105362-1-hugo@hugovil.com
Signed-off-by: Mark Brown <broonie@kernel.org>
drivers/regulator/core.c

index 2286bdf6edcbf4d351cad2df6504943669ccb6ef..dc5d67767336e0bc24c35efba07b884b91cb4c20 100644 (file)
@@ -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