From: Mark Brown <broonie@kernel.org>
To: Lee Jones <lee@kernel.org>
Cc: linux-kernel@vger.kernel.org,
"André Draszik" <andre.draszik@linaro.org>,
"Andy Shevchenko" <andy.shevchenko@gmail.com>,
"Bartosz Golaszewski" <brgl@kernel.org>,
"Charles Keepax" <ckeepax@opensource.cirrus.com>,
"ChiYuan Huang" <cy_huang@richtek.com>,
"Chris Morgan" <macromorgan@hotmail.com>,
"Douglas Anderson" <dianders@chromium.org>,
"Eduardo Candelaria" <jedu@slimlogic.co.uk>,
"Esteban Blanc" <eblanc@baylibre.com>,
"Graeme Gregory" <gg@slimlogic.co.uk>,
"Gyungoh Yoo" <jack.yoo@maxim-ic.com>,
"Jerome Neanne" <jneanne@baylibre.com>,
"Jiale Yao" <yaojiale02@163.com>,
"Kuninori Morimoto" <kuninori.morimoto.gx@renesas.com>,
"Laxman Dewangan" <ldewangan@nvidia.com>,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Linus Walleij" <linusw@kernel.org>,
"Mal Nadar" <m.nirmaladevi@ltts.com>,
"Matti Vaittinen" <mazziesaccount@gmail.com>,
"Stephen Warren" <swarren@nvidia.com>,
"Uday Khare" <udaykhare77@gmail.com>,
"Wentao Liang" <vulab@iscas.ac.cn>,
linux-gpio@vger.kernel.org, patches@opensource.cirrus.com
Subject: Re: [PATCH 00/10] regulator: Fix teardown races, reference counting, and error handling
Date: Thu, 05 Nov 2026 13:53:03 +0000 [thread overview]
Message-ID: <179388678317.2912885.6316009207520321878.b4-ty@b4> (raw)
In-Reply-To: <20261104182148.1176116-1-lee@kernel.org>
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
prev parent reply other threads:[~2026-11-06 10:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 18:20 Lee Jones
2026-11-04 18:20 ` [PATCH 01/10] regulator: irq_helpers: Clear caller handle in regulator_irq_helper_cancel() Lee Jones
2026-11-05 7:58 ` Matti Vaittinen
2026-11-04 18:20 ` [PATCH 02/10] regulator: arizona-ldo1: Avoid double gpiod_put() on enable GPIO Lee Jones
2026-11-05 10:08 ` Charles Keepax
2026-11-04 18:20 ` [PATCH 03/10] regulator: core: Flush delayed disable_work before releasing supply in regulator_unregister() Lee Jones
2026-11-04 18:20 ` [PATCH 04/10] regulator: arizona-micsupp: Cancel check_cp_work on device teardown Lee Jones
2026-11-05 10:15 ` Charles Keepax
2026-11-04 18:20 ` [PATCH 05/10] regulator: core: Hold supply device reference until constraints are resolved in regulator_resolve_supply() Lee Jones
2026-11-05 17:28 ` André Draszik
2026-11-04 18:20 ` [PATCH 06/10] regulator: core: Use ktime_get_boottime() in set_machine_constraints() Lee Jones
2026-11-04 18:20 ` [PATCH 07/10] regulator: bq257xx: Propagate GPIO error in bq257xx_reg_dt_parse_gpio() Lee Jones
2026-11-04 18:20 ` [PATCH 08/10] regulator: tps6594-regulator: Fix LDO4 n_voltages in tps6594_ldo_regs Lee Jones
2026-11-04 18:20 ` [PATCH 09/10] regulator: max8907: Avoid NULL idata dereference in max8907_regulator_probe() Lee Jones
2026-11-04 18:21 ` [PATCH 10/10] regulator: rt6190: Check pm_runtime_resume_and_get() return value in rt6190_out_enable() Lee Jones
2026-11-05 13:53 ` Mark Brown [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=179388678317.2912885.6316009207520321878.b4-ty@b4 \
--to=broonie@kernel.org \
--cc=andre.draszik@linaro.org \
--cc=andy.shevchenko@gmail.com \
--cc=brgl@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=cy_huang@richtek.com \
--cc=dianders@chromium.org \
--cc=eblanc@baylibre.com \
--cc=gg@slimlogic.co.uk \
--cc=jack.yoo@maxim-ic.com \
--cc=jedu@slimlogic.co.uk \
--cc=jneanne@baylibre.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=ldewangan@nvidia.com \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.nirmaladevi@ltts.com \
--cc=macromorgan@hotmail.com \
--cc=mazziesaccount@gmail.com \
--cc=patches@opensource.cirrus.com \
--cc=swarren@nvidia.com \
--cc=udaykhare77@gmail.com \
--cc=vulab@iscas.ac.cn \
--cc=yaojiale02@163.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®