Re: [PATCH 0/3] regulator: mpq4210: Address the post-merge review comments

[Mark Brown]

On Sun, 13 Sep 2026 11:40:15 +0000, Tapio Reijonen wrote:
> regulator: mpq4210: Address the post-merge review comments
> 
> The MPQ4210 series was applied to for-7.4 as e3c05a881fc9 and 61879d561e91,
> and two review comments arrived afterwards. Both are addressed here as
> incremental patches against current for-7.4.
> 
> Patches 1 and 2 rename mps,fb-voltage-divider to mps,fb-voltage-divider-ohms,
> as Krzysztof asked. The split across the binding and the driver leaves one
> commit where the two disagree, so they are meant to be applied together. The
> suffix is worth more here than the convention alone: mps,mp886x.yaml already
> describes a property of the same name whose values are kilo ohms rather than
> ohms, so two bindings from the same vendor spelled the resistances
> identically while meaning different units. Nothing in tree uses the old name
> and it has not appeared in a release, so no fallback is kept.
> 
> [...]

Applied to

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

Thanks!

[1/3] regulator: dt-bindings: mps,mpq4210: Use the -ohms unit suffix
      https://git.kernel.org/broonie/regulator/c/7a145b72280c
[2/3] regulator: mpq4210: Use the -ohms feedback divider property
      https://git.kernel.org/broonie/regulator/c/69bd71e55b71
[3/3] regulator: mpq4210: Drop the mod_devicetable.h include
      https://git.kernel.org/broonie/regulator/c/4cc0c5739ab8

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