linux-kernel - Re: (subset) [PATCH v4 0/3] Add support for MT6315 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:   Mon, 08 Feb 2021 18:39:43 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Hsin-Hsiung Wang <hsin-hsiung.wang@...iatek.com>,
        drinkcat@...omium.org, Matthias Brugger <matthias.bgg@...il.com>,
        Rob Herring <robh+dt@...nel.org>,
        Liam Girdwood <lgirdwood@...il.com>
Cc:     linux-mediatek@...ts.infradead.org,
        linux-arm-kernel@...ts.infradead.org,
        Project_Global_Chrome_Upstream_Group@...iatek.com,
        srv_heupstream@...iatek.com, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: (subset) [PATCH v4 0/3] Add support for MT6315 regulator

On Sun, 7 Feb 2021 14:14:14 +0800, Hsin-Hsiung Wang wrote:
> This patch series adds support for MediaTek PMIC MT6315 regulator driver,
> which adds MT6315 related buck voltage data to the driver.
> This series is based on below patch[1].
> 
> [1] https://patchwork.kernel.org/project/linux-mediatek/list/?series=429385
> 
> changes since v3:
> - fix the error of binding document.
> - refine the mt6315 regulator for better code quality.
> - update mt6315 regulator node in the mt8192-evb.dts.
> 
> [...]

Applied to

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

Thanks!

[1/3] dt-bindings: regulator: document binding for MT6315 regulator
      commit: 977fb5b58469c1367aa075e7e913c03cba7d466f
[2/3] regulator: mt6315: Add support for MT6315 regulator
      commit: 7aa382cfe714f61b0c29f02c31d389c506b4e2ae

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