Skip to contentSkip to conversation

regulator: max77620: drop redundant OF node initialisation

PATCH In review Johan Hovold 2 participants 2 messages Apr 7 – Apr 10 Voltage and current regulator framework

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 regulator: max77620: drop redundant OF node initialisation

The platform device OF node is set unconditionally since commit 6f55c5dd1118 ("regulator: max77620: Use device_set_of_node_from_dev()") so drop the earlier redundant conditional initialisation.

---
 drivers/regulator/max77620-regulator.c | 2 --
 1 file changed, 2 deletions(-)
drivers/regulator/max77620-regulator.c +0 -2
index 7bc87d8e9f68..57c54472ec5b 100644
@@ -793,8 +793,6 @@ static int max77620_regulator_probe(struct platform_device *pdev)
 	platform_set_drvdata(pdev, pmic);
 	pmic->dev = dev;
 	pmic->rmap = max77620_chip->rmap;
-	if (!dev->of_node)
-		dev->of_node = pdev->dev.parent->of_node;
 
 	switch (max77620_chip->chip_id) {
 	case MAX77620:
Signature · 1 line
2.52.0
maintainer
#1 lore raw
Quoted 1 line · Johan Hovold

regulator: max77620: drop redundant OF node initialisation

Applied to

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

Thanks!

[1/1] regulator: max77620: drop redundant OF node initialisation

      https://git.kernel.org/broonie/regulator/c/606c780b8843

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