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] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 27 Nov 2023 16:48:29 +0000
From:   Mark Brown <>
To:     Mark Rutland <>,
        Lorenzo Pieralisi <>,
        Sebastian Reichel <>,
        Karol Gugala <>,
        Mateusz Holenko <>,
        Gabriel Somlo <>,
        Joel Stanley <>,
        Orson Zhai <>,
        Baolin Wang <>,
        Chunyan Zhang <>,
        Lee Jones <>,
        Dmitry Osipenko <>,
        Andrew Davis <>
Subject: Re: (subset) [PATCH RFC 0/5] Deprecate register_restart_handler()

On Fri, 17 Nov 2023 10:10:01 -0600, Andrew Davis wrote:
> Explanation is in patch #1.
> The rest of this series is a set of representative examples of converting
> away from the old API. They should be valid and can be taken by their
> respective maintainers even if patch #1 doesn't find acceptance.
> Thanks,
> Andrew
> [...]

Applied to for-next


[4/5] spi: sprd: adi: Use devm_register_restart_handler()
      commit: 8e6a43961f24cf841d3c0d199521d0b284d948b9

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.


Powered by blists - more mailing lists