linux-kernel - Re: [PATCH v3 0/2] regulator: richtek,rt4801: parse GPIOs per regulator

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]

Date:   Mon, 25 Apr 2022 16:01:05 +0100
From:   Mark Brown <broonie@...nel.org>
To:     linux-kernel@...r.kernel.org, cy_huang@...htek.com,
        lgirdwood@...il.com, robh+dt@...nel.org,
        krzysztof.kozlowski@...aro.org, krzysztof.kozlowski+dt@...aro.org,
        devicetree@...r.kernel.org
Subject: Re: [PATCH v3 0/2] regulator: richtek,rt4801: parse GPIOs per regulator

On Mon, 25 Apr 2022 09:24:53 +0200, Krzysztof Kozlowski wrote:
> Not tested.
> 
> Follow up of discussion:
> https://lore.kernel.org/all/2d124d53-1f36-5315-3877-af8f8ad5f824@linaro.org/#t
> 
> Changes since v2
> ================
> Patch 2: Do not use core's ena_gpiod feature because of lost voltage issue
>          (ChiYuan Huang).
> 
> [...]

Applied to

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

Thanks!

[1/2] regulator: dt-bindings: richtek,rt4801: use existing ena_gpiod feature
      commit: a498db69dc6d7511d76a4f04ec19c5e378db1c3b
[2/2] regulator: richtek,rt4801: parse GPIOs per regulator
      commit: 6963569103c02b22076da245b19bd081d8da8f9e

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