On Sun, 07 May 2023 16:46:56 +0200, Krzysztof Kozlowski wrote: > The driver's probe() first registers regulators in a loop and then in a > second loop passes them as irq data to the interrupt handlers. However > the function to get the regulator for given name > tps65219_get_rdev_by_name() was a no-op due to argument passed by value, > not pointer, thus the second loop assigned always same value - from > previous loop. The interrupts, when fired, where executed with wrong > data. Compiler also noticed it: > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next Thanks! [1/1] regulator: tps65219: Fix matching interrupts for their regulators commit: f050e56de80591fee55bedbdf5b6b998c740cd0c 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
