Re: [PATCH v5 0/4] Qualcomm labibb regulator driver

[Mark Brown <broonie@kernel.org>]

On Mon, 22 Jun 2020 18:11:06 +0530, Sumit Semwal wrote:
> This series adds a driver for LAB/IBB regulators found on some Qualcomm SoCs.
> These regulators provide positive and/or negative boost power supplies
> for LCD/LED display panels connected to the SoC.
> 
> This series adds the support for pmi8998 PMIC found in SDM845 family of SoCs.
> 
> Changes from v4:
> - v4 Review comments incorporated
>   - simplified the driver: removed of_get_child_by_name(); use ENABLE_CTL
>     register and switch over to use the regulator_*_regmap helpers
>   - improved kerneldoc
>   - From the dt-bindings, removed interrupt-names, changed to dual license,
>     added unevaluatedProperties: false, removed interrupt-names, since there
>     is only one interrupt per node
>   - Since the Short Circuit handling needs more details from QC engineers,
>     drop the SC handling patch from this series, to submit it later
> 
> [...]

Applied to

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

Thanks!

[1/3] regulator: Allow regulators to verify enabled during enable()
      commit: f7d7ad42a9dc2d63cab6a79fe31e6732a30dacf5
[2/3] regulator: Add labibb regulator binding
      commit: 88c14de2b6786ef503fd1bc2c952159e65fe45cc
[3/3] regulator: qcom: Add labibb driver
      commit: 498ab2fdf8554690c9567c1eee436b858637e3ff

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