[PATCH] regulator: core: fix typo in comments

[PATCH] regulator: core: fix typo in comments

[Hugo Villeneuve]

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

Re: [PATCH] regulator: core: fix typo in comments

[Mark Brown]

On Mon, 23 Mar 2026 10:03:35 -0400, Hugo Villeneuve wrote:
> regulator: core: fix typo in comments

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-7.1

Thanks!

[1/1] regulator: core: fix typo in comments
      https://git.kernel.org/broonie/regulator/c/09a1361db3ab

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark