linux-kernel - Re: [PATCH 0/2] regulator: add support for SY8827N regulator

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Thu, 02 Jul 2020 16:46:52 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Rob Herring <robh+dt@...nel.org>,
        Jisheng Zhang <Jisheng.Zhang@...aptics.com>,
        Liam Girdwood <lgirdwood@...il.com>
Cc:     devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] regulator: add support for SY8827N regulator

On Thu, 2 Jul 2020 17:13:04 +0800, Jisheng Zhang wrote:
> The SY8827N from Silergy Corp is a single output DC/DC converter. The
> voltage can be controlled via I2C.
> 
> Jisheng Zhang (2):
>   dt-bindings: regulator: add document bindings for sy8827n
>   regulator: add support for SY8827N regulator
> 
> [...]

Applied to

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

Thanks!

[1/2] regulator: add document bindings for sy8827n
      commit: 573016266e6767f7917feeda8e1e3b19673f4981
[2/2] regulator: add support for SY8827N regulator
      commit: 38fc6f295726366a0135ca87ab98f3ab92afd81f

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