linux-kernel - Re: [PATCH v2] regulator: rtq6752: Enclose 'enable' gpio control by enable flag

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: <163171917481.10120.6058854376664686447.b4-ty@kernel.org>
Date:   Wed, 15 Sep 2021 16:21:41 +0100
From:   Mark Brown <broonie@...nel.org>
To:     cy_huang <u0084500@...il.com>
Cc:     Mark Brown <broonie@...nel.org>, lgirdwood@...il.com,
        cy_huang@...htek.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] regulator: rtq6752: Enclose 'enable' gpio control by enable flag

On Tue, 14 Sep 2021 22:20:49 +0800, cy_huang wrote:
> From: ChiYuan Huang <cy_huang@...htek.com>
> 
> Fix 'enable' gpio control logic from the below cases if it's specified.
> 
> 1. All off and both are sequentially controlled to be on.
> The 'enable' gpio control block to be called twice including the delay time.
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: rtq6752: Enclose 'enable' gpio control by enable flag
      commit: 6f3a9b100379320d27f4a64fa90f58101c95c5a8

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