[PATCH] regulator: rt6160: Remove dummy line and add module description

[PATCH] regulator: rt6160: Remove dummy line and add module description

[cy_huang]

From: ChiYuan Huang <cy_huang@richtek.com>

Remove dummy line and add module description.

Signed-off-by: ChiYuan Huang <cy_huang@richtek.com>
---
 drivers/regulator/rt6160-regulator.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/regulator/rt6160-regulator.c b/drivers/regulator/rt6160-regulator.c
index 4588ae0..1d18e4d 100644
--- a/drivers/regulator/rt6160-regulator.c
+++ b/drivers/regulator/rt6160-regulator.c
@@ -77,7 +77,6 @@ static int rt6160_disable(struct regulator_dev *rdev)
 	gpiod_set_value_cansleep(priv->enable_gpio, 0);
 
 	return 0;
-
 }
 
 static int rt6160_is_enabled(struct regulator_dev *rdev)
@@ -328,5 +327,6 @@ static struct i2c_driver rt6160_driver = {
 };
 module_i2c_driver(rt6160_driver);
 
+MODULE_DESCRIPTION("Richtek RT6160 voltage regulator driver");
 MODULE_AUTHOR("ChiYuan Huang <cy_huang@richtek.com>");
 MODULE_LICENSE("GPL v2");
-- 
2.7.4

Re: [PATCH] regulator: rt6160: Remove dummy line and add module description

[Mark Brown]

On Thu, 10 Jun 2021 22:38:30 +0800, cy_huang wrote:
> Remove dummy line and add module description.

Applied to

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

Thanks!

[1/1] regulator: rt6160: Remove dummy line and add module description
      commit: 23f95199b6446f828bf879ca316f388893435faa

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