uapi: regulator: Fix typo
PATCH 1/1 uapi: regulator: Fix typo
Fix minor typo.
--- include/uapi/regulator/regulator.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
include/uapi/regulator/regulator.h +1 -1
@@ -52,7 +52,7 @@/* * Following notifications should be emitted only if detected condition * is such that the HW is likely to still be working but consumers should -* take a recovery action to prevent problems esacalating into errors. +* take a recovery action to prevent problems escalating into errors. */ #define REGULATOR_EVENT_UNDER_VOLTAGE_WARN 0x2000#define REGULATOR_EVENT_OVER_CURRENT_WARN 0x4000
base-commit: 67ba055dd7758c34f6e64c9d35132362c1e1f0b5
Signature · 1 line
2.41.0
Quoted 12 lines · Naresh Solanki
Fix minor typo.
Signed-off-by Naresh Solanki <[email protected]>--- include/uapi/regulator/regulator.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)include/uapi/regulator/regulator.h +0
-0
include/uapi/regulator/regulator.h line 55
Quoted 5 lines
include/uapi/regulator/regulator.h +1
-1@@ -52,7 +52,7 @@/* * Following notifications should be emitted only if detected condition * is such that the HW is likely to still be working but consumers should -* take a recovery action to prevent problems esacalating into errors. +* take a recovery action to prevent problems escalating into errors.
Thanks!
Quoted 5 lines
include/uapi/regulator/regulator.h +0
-0*/ #define REGULATOR_EVENT_UNDER_VOLTAGE_WARN 0x2000#define REGULATOR_EVENT_OVER_CURRENT_WARN 0x4000base-commit:
67ba055dd7758c34f6e64c9d35132362c1e1f0b5
Signature · 5 lines
Matti Vaittinen Linux kernel developer at ROHM Semiconductors Oulu Finland ~~ When things go utterly wrong vim users can always type :help! ~~
Mark Brown
maintainerQuoted 3 lines · Naresh Solanki
Fix minor typo.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
Thanks!
[1/1] uapi: regulator: Fix typo
commit: 51088e5cc241178ccd6db2dd6d161dc8df32057d
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