linux-kernel - Re: [PATCH] regulator: rtq6752: fix reg reset behavior

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: <162644777059.26191.15104652877216907814.b4-ty@kernel.org>
Date:   Fri, 16 Jul 2021 16:05:28 +0100
From:   Mark Brown <broonie@...nel.org>
To:     cy_huang <u0084500@...il.com>
Cc:     Mark Brown <broonie@...nel.org>, lgirdwood@...il.com,
        linux-kernel@...r.kernel.org, ChiYuan Huang <cy_huang@...htek.com>,
        axel.lin@...ics.com
Subject: Re: [PATCH] regulator: rtq6752: fix reg reset behavior

On Fri, 16 Jul 2021 11:55:46 +0800, cy_huang wrote:
> Reg will be reset in below two conditions.
> 1. 'Enable' pin from H to L.
> 2. Both PAVDD and NAVDD are all disabled.
> 
> And 'Enable' pin also control i2c communication capability.
> 
> This patch is to Seperate the if condition in enable/disable callback for
> reg cache manipulation.

Applied to

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

Thanks!

[1/1] regulator: rtq6752: fix reg reset behavior
      commit: 513d14045a2dad0bf202b7d4c07a2ca2afdba0b4

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