linux-kernel - Re: [PATCH v3] dt-bindings: regulator: Convert Dialog DA9211 Regulators to DT schema

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: <176052181177.20825.9765115621999860948.b4-ty@kernel.org>
Date: Wed, 15 Oct 2025 10:50:11 +0100
From: Mark Brown <broonie@...nel.org>
To: angelogioacchino.delregno@...labora.com, conor+dt@...nel.org, 
 krzk+dt@...nel.org, lgirdwood@...il.com, robh@...nel.org, 
 support.opensource@...semi.com, 
 Ariel D'Alessandro <ariel.dalessandro@...labora.com>
Cc: devicetree@...r.kernel.org, kernel@...labora.com, 
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] dt-bindings: regulator: Convert Dialog DA9211
 Regulators to DT schema

On Wed, 01 Oct 2025 15:36:48 -0300, Ariel D'Alessandro wrote:
> Convert the existing text-based DT bindings for Dialog Semiconductor DA9211
> Voltage Regulators family to a DT schema. Examples are simplified, as these
> are all equal.
> 
> 

Applied to

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

Thanks!

[1/1] dt-bindings: regulator: Convert Dialog DA9211 Regulators to DT schema
      commit: 6277a486a7faaa6c87f4bf1d59a2de233a093248

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