linux-kernel - Re: [PATCH v11 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] [day] [month] [year] [list]

Message-Id: <158895800278.30774.16313316692034624719.b4-ty@kernel.org>
Date:   Fri, 08 May 2020 18:13:52 +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, lgirdwood@...il.com,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v11 00/11] Support ROHM BD99954 charger IC

On Thu, 7 May 2020 09:03:06 +0300, Matti Vaittinen wrote:
> Sorry folks for excessive amount of emails. I am resending this once
> more (I already resent v10 and v11 has no changes but was just rebased)
> because I am afraid the previous version did not reach Mark. If this is
> true - I am the one to blame. I see I sent original v10 to all other
> recipients and lists - except the LKML. So perhaps it evaded Mark's
> email filters. And the resend was also sent with the same message-id as
> original v10 so even though it did include the LKML it might still have
> gone unnoticed. I send this version to limited audience as it has no
> changes compared to original v10 - and it already has pretty much all
> the acks.
> 
> [...]

Applied to

   local tree regulator/for-5.7

Thanks!

[1/3] lib: add linear ranges helpers
      (no commit info)
[2/3] lib/test_linear_ranges: add a test for the 'linear_ranges'
      (no commit info)
[3/3] 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