linux-kernel - Re: [PATCH] regulator: mt6360: De-capitalize devicetree regulator subnodes

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <171268284879.51855.7043430433984734547.b4-ty@kernel.org>
Date: Tue, 09 Apr 2024 18:14:08 +0100
From: Mark Brown <broonie@...nel.org>
To: lgirdwood@...il.com, 
 AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>
Cc: matthias.bgg@...il.com, gene_chen@...htek.com, 
 linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, 
 linux-mediatek@...ts.infradead.org, kernel@...labora.com
Subject: Re: [PATCH] regulator: mt6360: De-capitalize devicetree regulator
 subnodes

On Tue, 09 Apr 2024 16:44:38 +0200, AngeloGioacchino Del Regno wrote:
> The MT6360 regulator binding, the example in the MT6360 mfd binding, and
> the devicetree users of those bindings are rightfully declaring MT6360
> regulator subnodes with non-capital names, and luckily without using the
> deprecated regulator-compatible property.
> 
> With this driver declaring capitalized BUCKx/LDOx as of_match string for
> the node names, obviously no regulator gets probed: fix that by changing
> the MT6360_REGULATOR_DESC macro to add a "match" parameter which gets
> assigned to the of_match.
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: mt6360: De-capitalize devicetree regulator subnodes
      commit: d3cf8a17498dd9104c04ad28eeac3ef3339f9f9f

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