[PATCH][next] regulator: rt5133: Fix spelling mistake "regualtor" -> "regulator"

[PATCH][next] regulator: rt5133: Fix spelling mistake "regualtor" -> "regulator"

[Colin Ian King]

There is a spelling mistake in a dev_err message. Fix it.

Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
---
 drivers/regulator/rt5133-regulator.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/regulator/rt5133-regulator.c b/drivers/regulator/rt5133-regulator.c
index d0f367381fbb..39532618e73d 100644
--- a/drivers/regulator/rt5133-regulator.c
+++ b/drivers/regulator/rt5133-regulator.c
@@ -511,7 +511,7 @@ static int rt5133_validate_vendor_info(struct rt5133_priv *priv)
 		}
 	}
 	if (IS_ERR(priv->cdata)) {
-		dev_err(priv->dev, "Failed to find regualtor match version\n");
+		dev_err(priv->dev, "Failed to find regulator match version\n");
 		return -ENODEV;
 	}
 
-- 
2.50.1

Re: [PATCH][next] regulator: rt5133: Fix spelling mistake "regualtor" -> "regulator"

[Mark Brown]

On Thu, 14 Aug 2025 08:33:26 +0100, Colin Ian King wrote:
> There is a spelling mistake in a dev_err message. Fix it.
> 
> 

Applied to

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

Thanks!

[1/1] regulator: rt5133: Fix spelling mistake "regualtor" -> "regulator"
      commit: 6d068f1ae2a2f713d7f21a9a602e65b3d6b6fc6d

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