linux-kernel - Re: [PATCH 1/3] regulator: dt-bindings: dlg,da9121: add buck2 constraints

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: <169032607621.1636970.15088372653295681523.b4-ty@kernel.org>
Date:   Wed, 26 Jul 2023 00:01:16 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Liam Girdwood <lgirdwood@...il.com>,
        Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Conor Dooley <conor+dt@...nel.org>,
        Support Opensource <support.opensource@...semi.com>,
        Paul Cercueil <paul@...pouillou.net>,
        Adam Ward <Adam.Ward.opensource@...semi.com>,
        linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
        Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Subject: Re: [PATCH 1/3] regulator: dt-bindings: dlg,da9121: add buck2
 constraints

On Tue, 25 Jul 2023 14:46:27 +0200, Krzysztof Kozlowski wrote:
> Instead of describing the constraints for some devices (buck2 not
> present), code it in allOf:if:then section to actually allow validation
> of this requirement.
> 
> 

Applied to

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

Thanks!

[1/3] regulator: dt-bindings: dlg,da9121: add buck2 constraints
      commit: 9b7e0645ba65e4824436a2f1817843291e744443
[2/3] regulator: dt-bindings: dlg,da9121: allow different names
      commit: e5481cc40d00b9f4a3250b2fd4a805e3d000b229
[3/3] regulator: dt-bindings: active-semi,act8846: correct supplies
      commit: 7631a0c5b093fe1bc27b4770021c4aa0d06fb3c5

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