linux-kernel - Re: [PATCH v2 1/5] dt-bindings: regulator: Add property for I2C level shifter

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: <165159306949.184265.18297673482925857388.b4-ty@kernel.org>
Date:   Tue, 03 May 2022 16:51:09 +0100
From:   Mark Brown <broonie@...nel.org>
To:     lgirdwood@...il.com, linux-kernel@...r.kernel.org,
        rickaran@...s.com
Cc:     rickard314.andersson@...il.com, perdo@...s.com
Subject: Re: [PATCH v2 1/5] dt-bindings: regulator: Add property for I2C level shifter

On Fri, 29 Apr 2022 09:22:07 +0200, Rickard Andersson wrote:
> From: Per-Daniel Olsson <perdo@...s.com>
> 
> By setting nxp,i2c-lt-enable the I2C level translator is
> enabled.
> 
> 

Applied to

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

Thanks!

[1/5] dt-bindings: regulator: Add property for I2C level shifter
      commit: e721b161399b30e085faa2f4b930ebeb15df36a7
[2/5] regulator: pca9450: Make I2C Level Translator configurable
      commit: 62139f52b7e588d565aa9df81ea0a0548a68b823
[3/5] dt-bindings: regulator: Add property for WDOG_B warm reset
      commit: bd2f5e71454bc84427c4fd67c5ea4881f155ac6e
[4/5] regulator: pca9450: Make warm reset on WDOG_B assertion
      commit: 2364a64d0673f5044e6a52cb17d6d60c6f1f8329
[5/5] regulator: pca9450: Enable DVS control via PMIC_STBY_REQ
      commit: 20078e3bbe6e5adb1a88f03f9609d532d99c690c

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