linux-kernel - Re: (subset) [PATCH v2 0/7] Add input voltage suppliers for PMIC MCP16502 regulators

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: <172356379435.80200.17658639217254735748.b4-ty@kernel.org>
Date: Tue, 13 Aug 2024 16:43:14 +0100
From: Mark Brown <broonie@...nel.org>
To: claudiu.beznea@...on.dev, lgirdwood@...il.com, 
 nicolas.ferre@...rochip.com, krzk+dt@...nel.org, conor+dt@...nel.org, 
 robh@...nel.org, alexandre.belloni@...tlin.com, 
 Andrei Simion <andrei.simion@...rochip.com>
Cc: linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org, 
 devicetree@...r.kernel.org
Subject: Re: (subset) [PATCH v2 0/7] Add input voltage suppliers for PMIC
 MCP16502 regulators

On Mon, 12 Aug 2024 16:52:24 +0300, Andrei Simion wrote:
> In this series of patches, support for the *-supply property [1]  is added
> (correlated with supply_name [2]) from the core regulator.
> Link [1]: https://github.com/torvalds/linux/blob/master/drivers/regulator/core.c#L471
> Link [2]: https://github.com/torvalds/linux/blob/master/drivers/regulator/core.c#L2064
> 
> I modified the mcp16502.c driver and the dts that use this PMIC.
> We added these improvements to provide a complete description of the board power scheme.
> 
> [...]

Applied to

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

Thanks!

[1/7] regulator: mcp16502: Add supplier for regulators
      commit: 861289835002b733aa8715442ba555b1daa84baa
[2/7] regulator: dt-bindings: microchip,mcp16502: Add voltage input supply documentation
      commit: bf5ba94fa0b90c9433167bf143780af6c8805479

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