linux-kernel - Re: [PATCH v3 0/4] mfd: lp87565: convert DT to yaml, ignore ENx pins and add LP87524-Q1

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

Message-Id: <159364222730.10880.1510321534507247340.b4-ty@kernel.org>
Date:   Wed, 01 Jul 2020 23:23:47 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Luca Ceresoli <luca@...aceresoli.net>,
        Liam Girdwood <lgirdwood@...il.com>
Cc:     Keerthy <j-keerthy@...com>, linux-kernel@...r.kernel.org,
        Lee Jones <lee.jones@...aro.org>, devicetree@...r.kernel.org,
        Rob Herring <robh+dt@...nel.org>,
        Axel Lin <axel.lin@...ics.com>
Subject: Re: [PATCH v3 0/4] mfd: lp87565: convert DT to yaml, ignore ENx pins and add LP87524-Q1

On Mon, 22 Jun 2020 22:43:25 +0200, Luca Ceresoli wrote:
> the first patch in this series is a small but significant variation in how
> the lp87565 driver enables the output rails, to allow the kernel to always
> know when it is enabling an output. However it can change existing
> behaviour (depending on the hardware setup) and thus it should be carefully
> evaluated.
> 
> The following patches are a fairly straightforward addition of a new chip
> variant along DT bindings conversion to yaml.
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: lp87565: enable voltage regardless of ENx pin
      commit: 81fdcef3a615f5d4ef2a2bd87a65d46f6816d687

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