linux-kernel - Re: [PATCH] regulator: qcom-rpmh: Fix PMR735a S3 regulator spec

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:   Wed, 16 Nov 2022 13:32:16 +0000
From:   Mark Brown <broonie@...nel.org>
To:     linux-arm-msm@...r.kernel.org,
        Konrad Dybcio <konrad.dybcio@...aro.org>, andersson@...nel.org,
        agross@...nel.org
Cc:     linux-kernel@...r.kernel.org, satya priya <skakit@...eaurora.org>,
        Liam Girdwood <lgirdwood@...il.com>,
        Matthias Kaehlcke <mka@...omium.org>,
        marijn.suijten@...ainline.org
Subject: Re: [PATCH] regulator: qcom-rpmh: Fix PMR735a S3 regulator spec

On Thu, 10 Nov 2022 22:07:05 +0100, Konrad Dybcio wrote:
> PMR735a has a wider range than previously defined. Fix it.
> 
> 

Applied to

   broonie/regulator.git for-next

Thanks!

[1/1] regulator: qcom-rpmh: Fix PMR735a S3 regulator spec
      commit: dd801b2265c81bf0c8b0b4b8f7c1e7bfed078403

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