Re: [PATCH 00/10] regulator: Fix teardown races, reference counting, and error handling

[Mark Brown]

On Wed, 04 Nov 2026 18:20:50 +0000, Lee Jones wrote:
> regulator: Fix teardown races, reference counting, and error handling
> 
> These issues were reported by Sashiko.
> 
> This series addresses ten bugs across the regulator core and regulator
> drivers:
> 
> [...]

Applied to

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

Thanks!

[01/10] regulator: irq_helpers: Clear caller handle in regulator_irq_helper_cancel()
        https://git.kernel.org/broonie/regulator/c/86dd1c48cec2
[02/10] regulator: arizona-ldo1: Avoid double gpiod_put() on enable GPIO
        https://git.kernel.org/broonie/regulator/c/2eb7501c91d3
[03/10] regulator: core: Flush delayed disable_work before releasing supply in regulator_unregister()
        https://git.kernel.org/broonie/regulator/c/e0ce6fe8f235
[04/10] regulator: arizona-micsupp: Cancel check_cp_work on device teardown
        https://git.kernel.org/broonie/regulator/c/e7cbbbfba41d
[05/10] regulator: core: Hold supply device reference until constraints are resolved in regulator_resolve_supply()
        https://git.kernel.org/broonie/regulator/c/b554fe98554c
[06/10] regulator: core: Use ktime_get_boottime() in set_machine_constraints()
        https://git.kernel.org/broonie/regulator/c/f6e7157f9369
[07/10] regulator: bq257xx: Propagate GPIO error in bq257xx_reg_dt_parse_gpio()
        https://git.kernel.org/broonie/regulator/c/a6e1a47ba91c
[08/10] regulator: tps6594-regulator: Fix LDO4 n_voltages in tps6594_ldo_regs
        https://git.kernel.org/broonie/regulator/c/4c03bc1cda05
[09/10] regulator: max8907: Avoid NULL idata dereference in max8907_regulator_probe()
        https://git.kernel.org/broonie/regulator/c/8c7542439d56
[10/10] regulator: rt6190: Check pm_runtime_resume_and_get() return value in rt6190_out_enable()
        https://git.kernel.org/broonie/regulator/c/a94cebd751c5

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