linux-kernel - Re: [PATCH 1/2] regulator: ab8500: Remove unused platform data

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]

Date:   Wed, 13 Jan 2021 15:28:00 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Liam Girdwood <lgirdwood@...il.com>,
        Linus Walleij <linus.walleij@...aro.org>
Cc:     Lee Jones <lee.jones@...aro.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] regulator: ab8500: Remove unused platform data

On Fri, 4 Dec 2020 15:03:41 +0100, Linus Walleij wrote:
> The struct ab8500_regulator_platform_data was a leftover
> since the days before we probed all regulators from the
> device tree. The ab8500-ext regulator was the only used,
> defining platform data and register intialization that
> was never used for anything, a copy of a boardfile no
> longer in use.
> 
> [...]

Applied to

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

Thanks!

[1/2] regulator: ab8500: Remove unused platform data
      commit: c512150b266b5d173c5ba841e9c09e4830ea4eca
[2/2] regulator: ab8500: Decomission platform data header
      commit: 3acb64c07e95a75dc0af0bc958f2d09a44a9fd0d

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