Re: [PATCH 0/7] regulator: Use scoped device node handling to simplify error paths

[Mark Brown <broonie@kernel.org>]

On Wed, 14 Aug 2024 17:04:04 +0200, Krzysztof Kozlowski wrote:
> Make code a bit smaller/simpler, with less of_node_put() thanks to
> cleanup.h.
> 
> Best regards,
> Krzysztof
> 

Applied to

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

Thanks!

[1/7] regulator: bd718x7: Use scoped device node handling to simplify error paths
      commit: 83c7cdeef5b22a73336eb18a59c7b4d63ec26659
[2/7] regulator: bd96801: Use scoped device node handling to simplify error paths
      commit: f372c262d4cfe31f0b67e8ae1a8ec9bf7c52d57b
[3/7] regulator: max8997: Use scoped device node handling to simplify error paths
      commit: ea13bd391d1b8f62ae2347bde7a174059d7f3f0d
[4/7] regulator: s5m8767: Use scoped device node handling to simplify error paths
      commit: 34a3f95941e0dfee750f2fd28faed4c8cd7ee42c
[5/7] regulator: qcom-rpmh: Simplify with scoped for each OF child loop
      commit: 17636d443fbe376d5192a7ce6a444aa45ce45541
[6/7] regulator: qcom-smd: Simplify with scoped for each OF child loop
      commit: d4cd75b8eff72d65dab63668d5d883d72dda0426
[7/7] regulator: scmi: Simplify with scoped for each OF child loop
      commit: 99cf5db9cdd39136fd5dbd10bda833aa0f870452

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