linux-kernel - Re: [PATCH v4] dt-bindings: regulator: twl-regulator: convert to yaml

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: <171768908601.1590050.10143046251745662528.b4-ty@kernel.org>
Date: Thu, 06 Jun 2024 16:51:26 +0100
From: Mark Brown <broonie@...nel.org>
To: lee@...nel.org, robh@...nel.org, krzk+dt@...nel.org, 
 conor+dt@...nel.org, lgirdwood@...il.com, devicetree@...r.kernel.org, 
 linux-kernel@...r.kernel.org, linux-omap@...r.kernel.org, 
 Andreas Kemnade <andreas@...nade.info>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Subject: Re: [PATCH v4] dt-bindings: regulator: twl-regulator: convert to
 yaml

On Thu, 06 Jun 2024 13:16:11 +0200, Andreas Kemnade wrote:
> Convert the regulator bindings to yaml.
> 
> Drop one twl5030 compatible due to no documentation on mfd side and no
> users of the twl5030.
> 
> 

Applied to

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

Thanks!

[1/1] dt-bindings: regulator: twl-regulator: convert to yaml
      commit: 62e4f339619701c4e16b47438ae7529532c28e23

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