mbox series

[v3,0/3] Add regulators support for PMX75

Message ID 1689062414-3654-1-git-send-email-quic_rohiagar@quicinc.com (mailing list archive)
Headers show
Series Add regulators support for PMX75 | expand

Message

Rohit Agarwal July 11, 2023, 8 a.m. UTC 
Hi,

Changes in v3:
 - Created a separate patch for updating the entry in pmx65 bindings.
 - Changed the subject of patches [1/3] and [2/3] according to the convention.

Changes in v2:
 - Addressed Krzysztof to update the if:then: in bindings patch.
 - Breaking the original series [1] into smaller series.

This series adds regulators supports in PMX75 found on
SDX75 platform.

[1] https://lore.kernel.org/all/1688395346-3126-1-git-send-email-quic_rohiagar@quicinc.com/

Thanks,
Rohit.

Rohit Agarwal (3):
  regulator: dt-bindings: qcom,rpmh: Update PMX65 entry
  regulator: dt-bindings: qcom,rpmh: Add PMX75 compatible
  regulator: qcom-rpmh: Add regulators support for PMX75

 .../bindings/regulator/qcom,rpmh-regulator.yaml    | 22 ++++++++++++-
 drivers/regulator/qcom-rpmh-regulator.c            | 38 ++++++++++++++++++++++
 2 files changed, 59 insertions(+), 1 deletion(-)

Comments

Mark Brown July 21, 2023, 2:44 p.m. UTC | #1 
On Tue, 11 Jul 2023 13:30:11 +0530, Rohit Agarwal wrote:
> Changes in v3:
>  - Created a separate patch for updating the entry in pmx65 bindings.
>  - Changed the subject of patches [1/3] and [2/3] according to the convention.
> 
> Changes in v2:
>  - Addressed Krzysztof to update the if:then: in bindings patch.
>  - Breaking the original series [1] into smaller series.
> 
> [...]

Applied to

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

Thanks!

[1/3] regulator: dt-bindings: qcom,rpmh: Update PMX65 entry
      commit: 4fdef8553df58953f572f1cb46d357c735c683a9
[2/3] regulator: dt-bindings: qcom,rpmh: Add PMX75 compatible
      commit: 0ef3d931632e3fce51ed5510935238937d644c97
[3/3] regulator: qcom-rpmh: Add regulators support for PMX75
      commit: 0b294ed669ead34a348d17d06b6d4d58712b14e2

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
Mark Brown July 25, 2023, 4:49 p.m. UTC | #2 
On Tue, 11 Jul 2023 13:30:11 +0530, Rohit Agarwal wrote:
> Changes in v3:
>  - Created a separate patch for updating the entry in pmx65 bindings.
>  - Changed the subject of patches [1/3] and [2/3] according to the convention.
> 
> Changes in v2:
>  - Addressed Krzysztof to update the if:then: in bindings patch.
>  - Breaking the original series [1] into smaller series.
> 
> [...]

Applied to

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

Thanks!

[1/3] regulator: dt-bindings: qcom,rpmh: Update PMX65 entry
      commit: 4fdef8553df58953f572f1cb46d357c735c683a9
[2/3] regulator: dt-bindings: qcom,rpmh: Add PMX75 compatible
      commit: 0ef3d931632e3fce51ed5510935238937d644c97
[3/3] regulator: qcom-rpmh: Add regulators support for PMX75
      commit: 0b294ed669ead34a348d17d06b6d4d58712b14e2

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