linux-kernel - Re: [PATCH 0/2] Fix rt4831 regulator active

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: <164824027262.2690421.16602981472244896326.b4-ty@kernel.org>
Date:   Fri, 25 Mar 2022 20:31:12 +0000
From:   Mark Brown <broonie@...nel.org>
To:     cy_huang <u0084500@...il.com>
Cc:     linux-kernel@...r.kernel.org, lucas_tsai@...htek.com,
        lgirdwood@...il.com, ChiYuan Huang <cy_huang@...htek.com>
Subject: Re: [PATCH 0/2] Fix rt4831 regulator active_discharge and bypass

On Fri, 25 Mar 2022 09:26:15 +0800, cy_huang wrote:
> From: ChiYuan Huang <cy_huang@...htek.com>
> 
> This patch series is to fix rt4831 regulator set/get active_discharge and bypass
> 
> ChiYuan Huang (2):
>   regulator: rt4831: Add bypass mask to fix set_bypass API work
>   regulator: rt4831: Add active_discharge_on to fix discharge API
> 
> [...]

Applied to

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

Thanks!

[1/2] regulator: rt4831: Add bypass mask to fix set_bypass API work
      commit: 184ae0e32bc990bba203b60503df89c9f8865f13
[2/2] regulator: rt4831: Add active_discharge_on to fix discharge API
      commit: aefe5fc3000a24869edbf7bb657adf28372ec158

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