linux-kernel - Re: [PATCH] regulator: dt-bindings: Clean-up active-semi,act8945a duplication

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: <175499674028.16220.7731759072204819862.b4-ty@kernel.org>
Date: Tue, 12 Aug 2025 12:05:40 +0100
From: Mark Brown <broonie@...nel.org>
To: Lee Jones <lee@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>, 
 Conor Dooley <conor+dt@...nel.org>, Sebastian Reichel <sre@...nel.org>, 
 Liam Girdwood <lgirdwood@...il.com>, Paul Cercueil <paul@...pouillou.net>, 
 "Rob Herring (Arm)" <robh@...nel.org>
Cc: devicetree@...r.kernel.org, linux-kernel@...r.kernel.org, 
 linux-pm@...r.kernel.org
Subject: Re: [PATCH] regulator: dt-bindings: Clean-up active-semi,act8945a
 duplication

On Thu, 07 Aug 2025 16:44:57 -0500, Rob Herring (Arm) wrote:
> The active-semi,act8945a binding is documented in multiple places. The
> charger child node is documented in regulator/active-semi,act8945a.yaml
> and power/supply/active-semi,act8945a-charger.yaml. An old text binding
> is in mfd/act8945a.txt.
> 
> Update the regulator/active-semi,act8945a.yaml with the additional
> descriptions and constraints from
> power/supply/active-semi,act8945a-charger.yaml, and then remove it and
> mfd/act8945a.txt.
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: dt-bindings: Clean-up active-semi,act8945a duplication
      commit: a54ef14188519a0994d0264f701f5771815fa11e

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