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  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:   Sat, 23 Oct 2021 20:58:03 +0100
From:   Mark Brown <>
To:     Liam Girdwood <>,
        Laxman Dewangan <>,
        Lee Jones <>,
        Alexandre Belloni <>,
        Dmitry Osipenko <>,
        Alessandro Zummo <>
Cc:     Mark Brown <>,,
Subject: Re: (subset) [PATCH v1 0/3] Remove TPS80031 driver

On Thu, 21 Oct 2021 22:22:55 +0300, Dmitry Osipenko wrote:
> TPS80031 driver was upstreamed back in 2013 and never got a user. I noticed
> that driver is abandoned while was about to write a patch to switch it to a
> new power-off API (that I'm working on). Driver requires platform data that
> nobody provides. Instead of changing the dead code, let's remove it.
> Dmitry Osipenko (3):
>   rtc: tps80031: Remove driver
>   regulator: tps80031: Remove driver
>   mfd: tps80031: Remove driver
> [...]

Applied to for-next


[2/3] regulator: tps80031: Remove driver
      commit: d7477e646291b2dcdd5521cf926cd390ddd6a7c1

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