linux-kernel - Re: [PATCH 1/2] regulator: max8893: add regulator driver

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: <162430087046.9551.11451976278911990353.b4-ty@kernel.org>
Date:   Mon, 21 Jun 2021 19:45:51 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Sergey Larin <cerg2010cerg2010@...l.ru>,
        Liam Girdwood <lgirdwood@...il.com>,
        Rob Herring <robh+dt@...nel.org>
Cc:     Mark Brown <broonie@...nel.org>, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] regulator: max8893: add regulator driver

On Fri, 18 Jun 2021 17:16:06 +0300, Sergey Larin wrote:
> MAX8893 is a simple regulator which can be found on some of Sasmsung
> phones.

Applied to

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

Thanks!

[1/2] regulator: max8893: add regulator driver
      commit: d83f778c627ad4e80bd82dbc88ffa1b1b18876bb
[2/2] dt-bindings: regulator: Add MAX8893 bindings
      commit: 01c5741b82969d096ac0870d997b7d2f5a5fe970

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