linux-kernel - Re: [PATCH v2] regulator: dt-bindings: qcom-labibb: Allow regulator-common properties

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: <167469295122.2698045.16881835440025059289.b4-ty@kernel.org>
Date:   Thu, 26 Jan 2023 00:29:11 +0000
From:   Mark Brown <broonie@...nel.org>
To:     linux-arm-msm@...r.kernel.org, andersson@...nel.org,
        agross@...nel.org, krzysztof.kozlowski@...aro.org,
        Konrad Dybcio <konrad.dybcio@...aro.org>
Cc:     marijn.suijten@...ainline.org, Liam Girdwood <lgirdwood@...il.com>,
        Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Sumit Semwal <sumit.semwal@...aro.org>,
        linux-kernel@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH v2] regulator: dt-bindings: qcom-labibb: Allow
 regulator-common properties

On Wed, 18 Jan 2023 19:18:10 +0100, Konrad Dybcio wrote:
> Allow regulator-common properties on lab/ibb regulators, such as
> regulator-always-on, etc.
> 
> 

Applied to

   broonie/regulator.git for-next

Thanks!

[1/1] regulator: dt-bindings: qcom-labibb: Allow regulator-common properties
      commit: 8966a72c1964f74e5a415fee8629f698ccb13342

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