linux-kernel - Re: [PATCH v4 0/4] MediaTek Helio X10 MT6795

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: <166308747505.261771.11158894502965288583.b4-ty@kernel.org>
Date:   Tue, 13 Sep 2022 17:44:35 +0100
From:   Mark Brown <broonie@...nel.org>
To:     AngeloGioacchino Del Regno 
        <angelogioacchino.delregno@...labora.com>
Cc:     krzysztof.kozlowski+dt@...aro.org, lgirdwood@...il.com,
        devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
        linux-mediatek@...ts.infradead.org,
        linux-arm-kernel@...ts.infradead.org, robh+dt@...nel.org,
        matthias.bgg@...il.com
Subject: Re: [PATCH v4 0/4] MediaTek Helio X10 MT6795 - MT6331/6332 Regulators

On Tue, 13 Sep 2022 14:34:52 +0200, AngeloGioacchino Del Regno wrote:
> In an effort to give some love to the apparently forgotten MT6795 SoC,
> I am upstreaming more components that are necessary to support platforms
> powered by this one apart from a simple boot to serial console.
> 
> This series adds support for the regulators found in MT6331 and MT6332
> main/companion PMICs.
> 
> [...]

Applied to

   broonie/regulator.git for-next

Thanks!

[1/4] dt-bindings: regulator: Add bindings for MT6331 regulator
      commit: 6385e21692bbb0b35eca8120d576b3c1ba1ad9d3
[2/4] regulator: Add driver for MT6331 PMIC regulators
      commit: 6f7a71f804287a7566314ab1a73d8ca2c18ca0d7
[3/4] dt-bindings: regulator: Add bindings for MT6332 regulator
      commit: e22943e32e1fc314b8e2b095ae3495d1bfa9aca5
[4/4] regulator: Add driver for MT6332 PMIC regulators
      commit: 1cc5a52e873a4f9725eafe5aa9cd213b7b58e29e

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