2020-07-06 08:10:33

by Axel Lin

[permalink] [raw]
Subject: [PATCH] regulator: fan53880: Add missing .owner field in regulator_desc

Add missing .owner field in regulator_desc, which is used for refcounting.

Signed-off-by: Axel Lin <[email protected]>
---
drivers/regulator/fan53880.c | 3 +++
1 file changed, 3 insertions(+)

diff --git a/drivers/regulator/fan53880.c b/drivers/regulator/fan53880.c
index 285acc705a55..575d289b8e04 100644
--- a/drivers/regulator/fan53880.c
+++ b/drivers/regulator/fan53880.c
@@ -45,6 +45,7 @@ static const struct regulator_ops fan53880_ops = {
.of_match = of_match_ptr("LDO"#_num), \
.regulators_node = of_match_ptr("regulators"), \
.type = REGULATOR_VOLTAGE, \
+ .owner = THIS_MODULE, \
.linear_ranges = (struct linear_range[]) { \
REGULATOR_LINEAR_RANGE(_default, 0x0, 0x0, 0), \
REGULATOR_LINEAR_RANGE(800000, 0xf, 0x73, 25000), \
@@ -69,6 +70,7 @@ static const struct regulator_desc fan53880_regulators[] = {
.of_match = of_match_ptr("BUCK"),
.regulators_node = of_match_ptr("regulators"),
.type = REGULATOR_VOLTAGE,
+ .owner = THIS_MODULE,
.linear_ranges = (struct linear_range[]) {
REGULATOR_LINEAR_RANGE(1100000, 0x0, 0x0, 0),
REGULATOR_LINEAR_RANGE(600000, 0x1f, 0xf7, 12500),
@@ -87,6 +89,7 @@ static const struct regulator_desc fan53880_regulators[] = {
.of_match = of_match_ptr("BOOST"),
.regulators_node = of_match_ptr("regulators"),
.type = REGULATOR_VOLTAGE,
+ .owner = THIS_MODULE,
.linear_ranges = (struct linear_range[]) {
REGULATOR_LINEAR_RANGE(5000000, 0x0, 0x0, 0),
REGULATOR_LINEAR_RANGE(3000000, 0x4, 0x70, 25000),
--
2.25.1


2020-07-06 14:44:19

by Mark Brown

[permalink] [raw]
Subject: Re: [PATCH] regulator: fan53880: Add missing .owner field in regulator_desc

On Mon, 6 Jul 2020 16:09:44 +0800, Axel Lin wrote:
> Add missing .owner field in regulator_desc, which is used for refcounting.

Applied to

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

Thanks!

[1/1] regulator: fan53880: Add missing .owner field in regulator_desc
commit: 6c814b676e8bab850b64ab76a035571773c65727

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