regulator: tps65218: Remove '.owner' field
Subsystems (2)
PATCH 1/1 regulator: tps65218: Remove '.owner' field
Remove '.owner' field of driver structure as it is going to be filled via "module_platform_driver" call.
---
:100644 100644 f0a4028... e2b97ac... M drivers/regulator/tps65218-regulator.c
drivers/regulator/tps65218-regulator.c | 1 - 1 file changed, 1 deletion(-)
drivers/regulator/tps65218-regulator.c +0 -1
@@ -255,7 +255,6 @@ static int tps65218_regulator_probe(struct platform_device *pdev)static struct platform_driver tps65218_regulator_driver = { .driver = { .name ="tps65218-pmic" , - .owner =THIS_MODULE , .of_match_table = tps65218_of_match, }, .probe = tps65218_regulator_probe,
Signature · 1 line
1.7.10.4
Mark Brown
maintainerQuoted 2 lines · Manish Badarkhe
Remove '.owner' field of driver structure as it is going to be filled via "
module_platform_driver" call.
Same question as ever with this stuff: if we've decided to do this why are we doing it for a single driver and not as a genric cleanup?
Hi Mark,
Quoted 6 lines · Mark Brown
Quoted 2 lines · Manish Badarkhe
Remove '.owner' field of driver structure as it is going to be filled via "
module_platform_driver" call.Same question as ever with this stuff: if we've decided to do this why are we doing it for a single driver and not as a genric cleanup?
There are many drivers needs to be changed with such fix. Can we fix drivers with this fix module by module or all at once? Please let me know your opinion.
Thanks
Manish Badarkhe
Mark Brown
maintainerQuoted 8 lines · Manish Badarkhe
Quoted 2 lines · Mark Brown
Same question as ever with this stuff: if we've decided to do this why are we doing it for a single driver and not as a genric cleanup?
There are many drivers needs to be changed with such fix. Can we fix drivers with this fix module by module or all at once? Please let me know your opinion.
All at once, though I think Greg just did that in -next anyway.