[PATCH] regulator: Kconfig: fix a typo

Felix Gu posted 1 patch 1 month, 3 weeks ago
drivers/regulator/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
[PATCH] regulator: Kconfig: fix a typo
Posted by Felix Gu 1 month, 3 weeks ago
Fixes a typo in Kconfig, HWWON -> HWMON

Signed-off-by: Felix Gu <ustc.gu@gmail.com>
---
 drivers/regulator/Kconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/regulator/Kconfig b/drivers/regulator/Kconfig
index a708fc63f581..d10b6f9243d5 100644
--- a/drivers/regulator/Kconfig
+++ b/drivers/regulator/Kconfig
@@ -508,7 +508,7 @@ config REGULATOR_FP9931
 	  This driver supports the FP9931/JD9930 voltage regulator chip
 	  which is used to provide power to Electronic Paper Displays
 	  so it is found in E-Book readers.
-	  If HWWON is enabled, it also provides temperature measurement.
+	  If HWMON is enabled, it also provides temperature measurement.
 
 config REGULATOR_LM363X
 	tristate "TI LM363X voltage regulators"

---
base-commit: 779cae956c8316aebc1946ef86ca001f99658270
change-id: 20260224-kconfig-458ce63b25da

Best regards,
-- 
Felix Gu <ustc.gu@gmail.com>
Re: [PATCH] regulator: Kconfig: fix a typo
Posted by Mark Brown 1 month, 2 weeks ago
On Tue, 24 Feb 2026 20:23:30 +0800, Felix Gu wrote:
> Fixes a typo in Kconfig, HWWON -> HWMON
> 
> 

Applied to

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

Thanks!

[1/1] regulator: Kconfig: fix a typo
      commit: bfd7db781e2e7a99b086d645a104d16e368f58ff

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