mbox series

[0/2] Add PM2250 qcom_smd regulators

Message ID 20210926084549.29880-1-shawn.guo@linaro.org
Headers show
Series Add PM2250 qcom_smd regulators | expand

Message

Shawn Guo Sept. 26, 2021, 8:45 a.m. UTC 
The series adds Qualcomm PM2250 smd-rpm regulators support.

Shawn Guo (2):
  dt-bindings: regulator: Document PM2250 smd-rpm regulators
  regulator: qcom_smd: Add PM2250 regulators

 .../regulator/qcom,smd-rpm-regulator.yaml     |  4 ++
 drivers/regulator/qcom_smd-regulator.c        | 49 +++++++++++++++++++
 2 files changed, 53 insertions(+)

Comments

Mark Brown Oct. 2, 2021, 12:16 a.m. UTC | #1 
On Sun, 26 Sep 2021 16:45:47 +0800, Shawn Guo wrote:
> The series adds Qualcomm PM2250 smd-rpm regulators support.
> 
> Shawn Guo (2):
>   dt-bindings: regulator: Document PM2250 smd-rpm regulators
>   regulator: qcom_smd: Add PM2250 regulators
> 
> .../regulator/qcom,smd-rpm-regulator.yaml     |  4 ++
>  drivers/regulator/qcom_smd-regulator.c        | 49 +++++++++++++++++++
>  2 files changed, 53 insertions(+)
> 
> [...]

Applied to

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

Thanks!

[1/2] dt-bindings: regulator: Document PM2250 smd-rpm regulators
      commit: 482f8032f496d8fa1441da742fd57fadbb17fb3d
[2/2] regulator: qcom_smd: Add PM2250 regulators
      commit: 400c93151f4160cf75e065d40e3774a18c8555a0

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