linux-kernel - Re: (subset) [PATCH v8 01/11] dt-bindings: mfd: Initial commit of silergy,sy7636a.yaml

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <162803004553.42325.11270112719956797147.b4-ty@kernel.org>
Date:   Tue,  3 Aug 2021 23:35:33 +0100
From:   Mark Brown <broonie@...nel.org>
To:     kernel@...gutronix.de, lee.jones@...aro.org, robh+dt@...nel.org,
        lgirdwood@...il.com, Alistair Francis <alistair@...stair23.me>,
        linux-imx@....com
Cc:     Mark Brown <broonie@...nel.org>, alistair23@...il.com,
        devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: (subset) [PATCH v8 01/11] dt-bindings: mfd: Initial commit of silergy,sy7636a.yaml

On Tue, 3 Aug 2021 18:44:48 +1000, Alistair Francis wrote:
> Initial support for the Silergy SY7636A Power Management chip
> and regulator.

Applied to

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

Thanks!

[05/11] regulator: sy7636a: Remove the poll_enable_time
        commit: e5dad32d90e0e9b006f5c330e92fa0ec9042ae79
[06/11] regulator: sy7636a: Use the parent driver data
        commit: 4cafe1aeb5fb4eb1778d5e1b91d50a078369dbe1
[07/11] regulator: sy7636a: Store the epd-pwr-good GPIO locally
        commit: d38d49b140043bba3ea27b89cca5fefaf08e2034

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