linux-kernel - Re: [PATCH 0/2] Add input_supply support in gpio_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]

Message-Id: <166446672840.175965.2897291078173491886.b4-ty@kernel.org>
Date:   Thu, 29 Sep 2022 16:52:08 +0100
From:   Mark Brown <broonie@...nel.org>
To:     krzysztof.kozlowski+dt@...aro.org, lgirdwood@...il.com,
        Jerome Neanne <jneanne@...libre.com>, robh+dt@...nel.org
Cc:     linux-kernel@...r.kernel.org, khilman@...libre.com,
        msp@...libre.com, devicetree@...r.kernel.org
Subject: Re: [PATCH 0/2] Add input_supply support in gpio_regulator_config

On Thu, 29 Sep 2022 15:25:24 +0200, Jerome Neanne wrote:
> This is simillar needs and implementation as fixed-regulator.
> Used to extract regulator parent from the device tree.
> 
> Provide implementation and bindings for vin-supply property.
> 
> Jerome Neanne (2):
>   regulator: gpio: Add input_supply support in gpio_regulator_config
>   dt-bindings: gpio-regulator: add vin-supply property support
> 
> [...]

Applied to

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

Thanks!

[1/2] regulator: gpio: Add input_supply support in gpio_regulator_config
      commit: adfdfcbdbd32b356323a3db6d3a683270051a7e6
[2/2] dt-bindings: gpio-regulator: add vin-supply property support
      commit: 392cc0a4a0c4b25534f3148b192f18be468f67bd

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