linux-kernel - Re: [PATCH] regulator: qcom-smd: make smd_vreg

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: <172772865733.2147169.16731345779366535012.b4-ty@kernel.org>
Date: Mon, 30 Sep 2024 21:37:37 +0100
From: Mark Brown <broonie@...nel.org>
To: Liam Girdwood <lgirdwood@...il.com>, 
 Konrad Dybcio <konradybcio@...nel.org>, 
 Min-Hua Chen <minhuadotchen@...il.com>
Cc: linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] regulator: qcom-smd: make smd_vreg_rpm static

On Fri, 27 Sep 2024 07:10:36 +0800, Min-Hua Chen wrote:
> Since smd_vreg_rpm is used only in
> drivers/regulator/qcom_smd-regulator.c, make it static and fix the
> following sparse warning:
> 
> drivers/regulator/qcom_smd-regulator.c:14:21: sparse: warning:
> symbol 'smd_vreg_rpm' was not declared. Should it be static?
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: qcom-smd: make smd_vreg_rpm static
      commit: 18be43aca2c0ec475037923a8086d0a29fcc9d16

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