Re: [PATCH v2] regulator: core: fix kobject release warning and memory leak in regulator_register()

From: Mark Brown
Date: Wed Nov 16 2022 - 08:14:23 EST


On Wed, 16 Nov 2022 15:43:39 +0800, Zeng Heng wrote:
> Here is a warning report about lack of registered release()
> from kobject lib:
>
> Device '(null)' does not have a release() function, it is broken and must be fixed.
> WARNING: CPU: 0 PID: 48430 at drivers/base/core.c:2332 device_release+0x104/0x120
> Call Trace:
> kobject_put+0xdc/0x180
> put_device+0x1b/0x30
> regulator_register+0x651/0x1170
> devm_regulator_register+0x4f/0xb0
>
> [...]

Applied to

broonie/regulator.git for-next

Thanks!

[1/1] regulator: core: fix kobject release warning and memory leak in regulator_register()
commit: 5f4b204b6b8153923d5be8002c5f7082985d153f

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