linux-kernel - Re: [PATCH] regulator: spacemit: Align input supply name with the DT binding

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: <176527571370.622933.17720204195171811423.b4-ty@kernel.org>
Date: Tue, 09 Dec 2025 19:21:53 +0900
From: Mark Brown <broonie@...nel.org>
To: linux-kernel@...r.kernel.org, 
 Javier Martinez Canillas <javierm@...hat.com>
Cc: Alex Elder <elder@...cstar.com>, Liam Girdwood <lgirdwood@...il.com>, 
 Yixun Lan <dlan@...too.org>, linux-riscv@...ts.infradead.org, 
 spacemit@...ts.linux.dev
Subject: Re: [PATCH] regulator: spacemit: Align input supply name with the
 DT binding

On Sat, 06 Dec 2025 14:38:48 +0100, Javier Martinez Canillas wrote:
> The Device Tree binding schema for the SpacemiT P1 PMIC defines the main
> input supply property as "vin-supply", but the driver defines the supply
> name for BUCK and ALDO regulators as "vcc".
> 
> This causes the regulator core to lookup for a non-existent "vcc-supply".
> Rename the supply from "vcc" to "vin", to match the DT binding and ensure
> that the regulators input supplies are correctly resolved.
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: spacemit: Align input supply name with the DT binding
      commit: 99f0c3a654c4a762aca4fadc8d9f8636b36d570a

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