linux-kernel - Re: [PATCH] regulator: pca9450: Use devm_register_sys_off

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <175561865504.183354.10100694727990904311.b4-ty@kernel.org>
Date: Tue, 19 Aug 2025 16:50:55 +0100
From: Mark Brown <broonie@...nel.org>
To: Liam Girdwood <lgirdwood@...il.com>, 
 Paul Geurts <paul.geurts@...drive-technologies.com>, 
 Peng Fan <peng.fan@....com>
Cc: linux-kernel@...r.kernel.org
Subject: Re: [PATCH] regulator: pca9450: Use devm_register_sys_off_handler

On Fri, 15 Aug 2025 12:52:09 +0800, Peng Fan wrote:
> With module test, there is error dump:
> ------------[ cut here ]------------
>   notifier callback pca9450_i2c_restart_handler already registered
>   WARNING: kernel/notifier.c:23 at notifier_chain_register+0x5c/0x88,
>   CPU#0: kworker/u16:3/50
>   Call trace:
>   notifier_chain_register+0x5c/0x88 (P)
>   atomic_notifier_chain_register+0x30/0x58
>   register_restart_handler+0x1c/0x28
>   pca9450_i2c_probe+0x418/0x538
>   i2c_device_probe+0x220/0x3d0
>   really_probe+0x114/0x410
>   __driver_probe_device+0xa0/0x150
>   driver_probe_device+0x40/0x114
>   __device_attach_driver+0xd4/0x12c
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: pca9450: Use devm_register_sys_off_handler
      commit: 447be50598c05499f7ccc2b1f6ddb3da30f8099a

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