[PATCH] regulator: fp9931: Fix spelling mistake "failid" -> "failed"

Colin Ian King posted 1 patch 3 days, 4 hours ago
drivers/regulator/fp9931.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
[PATCH] regulator: fp9931: Fix spelling mistake "failid" -> "failed"
Posted by Colin Ian King 3 days, 4 hours ago
There is a spelling mistake in a dev_err_probe message. Fix it.

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

diff --git a/drivers/regulator/fp9931.c b/drivers/regulator/fp9931.c
index 875d875d1a50..fef0bb07fd5d 100644
--- a/drivers/regulator/fp9931.c
+++ b/drivers/regulator/fp9931.c
@@ -444,7 +444,7 @@ static int fp9931_probe(struct i2c_client *client)
 	data->vin_reg = devm_regulator_get_optional(&client->dev, "vin");
 	if (IS_ERR(data->vin_reg))
 		return dev_err_probe(&client->dev, PTR_ERR(data->vin_reg),
-				     "failid to get vin regulator\n");
+				     "failed to get vin regulator\n");
 
 	data->pgood_gpio = devm_gpiod_get(&client->dev, "pg", GPIOD_IN);
 	if (IS_ERR(data->pgood_gpio))
-- 
2.51.0
Re: [PATCH] regulator: fp9931: Fix spelling mistake "failid" -> "failed"
Posted by Mark Brown 2 days, 23 hours ago
On Fri, 28 Nov 2025 17:33:29 +0000, Colin Ian King wrote:
> There is a spelling mistake in a dev_err_probe message. Fix it.
> 
> 

Applied to

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

Thanks!

[1/1] regulator: fp9931: Fix spelling mistake "failid" -> "failed"
      commit: 81d431130ae1af4e64030f6a956ee9137e6fc1b0

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