linux-kernel - Re: [PATCH v12 00/11] Support ROHM BD99954 charger IC

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <158895800278.30774.18266282191247434212.b4-ty@kernel.org>
Date:   Fri, 08 May 2020 18:13:46 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Matti Vaittinen <matti.vaittinen@...rohmeurope.com>,
        mazziesaccount@...il.com
Cc:     sre@...nel.org, linux-pm@...r.kernel.org,
        brendanhiggins@...gle.com, linux-kernel@...r.kernel.org,
        lgirdwood@...il.com
Subject: Re: [PATCH v12 00/11] Support ROHM BD99954 charger IC

On Fri, 8 May 2020 18:38:17 +0300, Matti Vaittinen wrote:
> Please note that this series should be applied to two trees. Patches
> 1-4 (or 1-5 as suggested by Sebastian) should go to regulator tree.
> Perhaps Mark can provide an immutable branch to Sebastian? Rest of the
> patches can then go to power-supply tree.
> 
> Support ROHM BD99954 Battery Management IC
> 
> [...]

Applied to

   local tree regulator/for-5.7

Thanks!

[1/4] lib: add linear ranges helpers
      (no commit info)
[2/4] lib/test_linear_ranges: add a test for the 'linear_ranges'
      (no commit info)
[3/4] power: supply: bd70528: rename linear_range to avoid collision
      (no commit info)
[4/4] regulator: use linear_ranges helper
      (no commit info)

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