linux-kernel - Re: [RESEND PATCH] regulator: set of

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: <159777237821.25048.6743477910042149752.b4-ty@kernel.org>
Date:   Tue, 18 Aug 2020 18:39:43 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Jonathan Marek <jonathan@...ek.ca>, linux-arm-msm@...r.kernel.org
Cc:     Liam Girdwood <lgirdwood@...il.com>,
        Wesley Cheng <wcheng@...eaurora.org>,
        Andy Gross <agross@...nel.org>,
        Bjorn Andersson <bjorn.andersson@...aro.org>,
        "open list:VOLTAGE AND CURRENT REGULATOR FRAMEWORK" 
        <linux-kernel@...r.kernel.org>
Subject: Re: [RESEND PATCH] regulator: set of_node for qcom vbus regulator

On Tue, 18 Aug 2020 12:25:08 -0400, Jonathan Marek wrote:
> This allows the regulator to be found by devm_regulator_get().
> 
> Fixes: 4fe66d5a62fb ("regulator: Add support for QCOM PMIC VBUS booster")

Applied to

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

Thanks!

[1/1] regulator: set of_node for qcom vbus regulator
      commit: 66c3b96a7bd042427d2e0eaa8704536828f8235f

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