linux-kernel - Re: (subset) [PATCH v1 0/2] Fix USB vdd info for IPQ9574

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <173878949554.299478.16607544866188543376.b4-ty@kernel.org>
Date: Wed, 05 Feb 2025 21:04:55 +0000
From: Mark Brown <broonie@...nel.org>
To: lgirdwood@...il.com, robh@...nel.org, krzk+dt@...nel.org, 
 conor+dt@...nel.org, andersson@...nel.org, konradybcio@...nel.org, 
 agross@...nel.org, dmitry.baryshkov@...aro.org, 
 linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org, 
 devicetree@...r.kernel.org, Varadarajan Narayanan <quic_varada@...cinc.com>
Subject: Re: (subset) [PATCH v1 0/2] Fix USB vdd info for IPQ9574

On Wed, 05 Feb 2025 13:16:55 +0530, Varadarajan Narayanan wrote:
> Use correct regulator for USB phy.
> 
> For some reason, the dt-bindings [1] patch posted and Acked long
> time back seems to have slipped through the cracks and hasn't
> been merged. Including it along with this patch as both are
> related. dt_binding_check & dtbs_check passed.
> 
> [...]

Applied to

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

Thanks!

[1/2] regulator: qcom_smd: Add l2, l5 sub-node to mp5496 regulator
      commit: b0eddc21900fb44f8c5db95710479865e3700fbd

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