[PATCH] regulator: rtq6752: Fix the typo for reg define and author name

[PATCH] regulator: rtq6752: Fix the typo for reg define and author name

[cy_huang]

From: ChiYuan Huang <cy_huang@richtek.com>

Fix the typo for reg define and author name.

Signed-off-by: ChiYuan Huang <cy_huang@richtek.com>
---
 drivers/regulator/rtq6752-regulator.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/regulator/rtq6752-regulator.c b/drivers/regulator/rtq6752-regulator.c
index fe31597..72a72aa 100644
--- a/drivers/regulator/rtq6752-regulator.c
+++ b/drivers/regulator/rtq6752-regulator.c
@@ -19,7 +19,7 @@ enum {
 #define RTQ6752_REG_PAVDD	0x00
 #define RTQ6752_REG_NAVDD	0x01
 #define RTQ6752_REG_PAVDDONDLY	0x07
-#define RTQ6752_REG_PAVDDSSTIME	0x07
+#define RTQ6752_REG_PAVDDSSTIME	0x08
 #define RTQ6752_REG_NAVDDONDLY	0x0D
 #define RTQ6752_REG_NAVDDSSTIME	0x0E
 #define RTQ6752_REG_OPTION1	0x12
@@ -280,6 +280,6 @@ static struct i2c_driver rtq6752_driver = {
 };
 module_i2c_driver(rtq6752_driver);
 
-MODULE_AUTHOR("ChiYuan Hwang <cy_huang@richtek.com>");
+MODULE_AUTHOR("ChiYuan Huang <cy_huang@richtek.com>");
 MODULE_DESCRIPTION("Richtek RTQ6752 Regulator Driver");
 MODULE_LICENSE("GPL v2");
-- 
2.7.4

Re: [PATCH] regulator: rtq6752: Fix the typo for reg define and author name

[Axel Lin]

cy_huang <u0084500@gmail.com> 於 2021年7月14日 週三 上午10:36寫道：
>
> From: ChiYuan Huang <cy_huang@richtek.com>
>
> Fix the typo for reg define and author name.
>
> Signed-off-by: ChiYuan Huang <cy_huang@richtek.com>
Reported-by: Axel Lin <axel.lin@ingics.com>

Re: [PATCH] regulator: rtq6752: Fix the typo for reg define and author name

[Mark Brown]

On Wed, 14 Jul 2021 10:36:10 +0800, cy_huang wrote:
> Fix the typo for reg define and author name.

Applied to

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

Thanks!

[1/1] regulator: rtq6752: Fix the typo for reg define and author name
      commit: 77eac0e1ce9c61b66c15f7cc503ae848b74fe42c

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