linux-kernel - Re: [PATCH 1/2] dt-bindings: regulator: qcom: Document PM8226 smd 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: <162072067395.33366.7650476255510624158.b4-ty@kernel.org>
Date:   Tue, 11 May 2021 09:25:42 +0100
From:   Mark Brown <broonie@...nel.org>
To:     linux-arm-msm@...r.kernel.org,
        Bjorn Andersson <bjorn.andersson@...aro.org>,
        Andy Gross <agross@...nel.org>,
        Bartosz Dudziak <bartosz.dudziak@...jp.pl>,
        Liam Girdwood <lgirdwood@...il.com>,
        devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
        Kathiravan T <kathirav@...eaurora.org>,
        Rob Herring <robh+dt@...nel.org>
Cc:     Mark Brown <broonie@...nel.org>
Subject: Re: [PATCH 1/2] dt-bindings: regulator: qcom: Document PM8226 smd regulator

On Sun, 2 May 2021 13:53:03 +0200, Bartosz Dudziak wrote:
> Document the PM8226 SMD-RPM regulator entry.

Applied to

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

Thanks!

[1/2] dt-bindings: regulator: qcom: Document PM8226 smd regulator
      commit: 00c8b0b1e6e1314bb57aab6438fbc2803c637d9d
[2/2] regulator: qcom_smd: Add PM8226 regulator support
      commit: 8c816d56a2a4e757bb121d1af4c04f47ac0572d3

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