linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>,
	Andy Gross <agross@kernel.org>, Rob Herring <robh+dt@kernel.org>,
	satya priya <skakit@codeaurora.org>
Cc: Mark Brown <broonie@kernel.org>,
	linux-kernel@vger.kernel.org, rnayak@codeaurora.org,
	Liam Girdwood <lgirdwood@gmail.com>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	kgunda@codeaurora.org
Subject: Re: [PATCH V3 0/5] Add PM7325/PM8350C/PMR735A regulator support
Date: Thu,  1 Apr 2021 21:43:17 +0100	[thread overview]
Message-ID: <161730974895.25526.12885475666064429104.b4-ty@kernel.org> (raw)
In-Reply-To: <1617192339-3760-1-git-send-email-skakit@codeaurora.org>

On Wed, 31 Mar 2021 17:35:34 +0530, satya priya wrote:
> This series is dependent on below series which adds DT files for SC7280 SoC
> https://lore.kernel.org/patchwork/project/lkml/list/?series=488871
> 
> satya priya (5):
>   regulator: qcom-rpmh: Add pmic5_ftsmps520 buck
>   regulator: qcom-rpmh: Add PM7325/PMR735A regulator support
>   arm64: dts: qcom: sc7280: Add RPMh regulators for sc7280-idp
>   dt-bindings: regulator: Convert RPMh regulator bindings to YAML
>   dt-bindings: regulator: Add compatibles for PM7325/PMR735A
> 
> [...]

Applied to

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

Thanks!

[1/5] regulator: qcom-rpmh: Add pmic5_ftsmps520 buck
      commit: 9405b4f7fa78b55fc83e5b5258f00e651aed5734
[2/5] regulator: qcom-rpmh: Add PM7325/PMR735A regulator support
      commit: c4e5aa3dbee56bde70dfa03debc49bf9494fb3d9
[3/5] arm64: dts: qcom: sc7280: Add RPMh regulators for sc7280-idp
      (no commit info)
[4/5] dt-bindings: regulator: Convert RPMh regulator bindings to YAML
      commit: 7255f98d08c73f0bcf1397d3060fdb776d7aa147
[5/5] dt-bindings: regulator: Add compatibles for PM7325/PMR735A
      commit: be724fd5b60dd083c8e39a4a2652e5017d2f7a20

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

      parent reply	other threads:[~2021-04-01 20:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-31 12:05 [PATCH V3 0/5] Add PM7325/PM8350C/PMR735A regulator support satya priya
2021-03-31 12:05 ` [PATCH V3 1/5] regulator: qcom-rpmh: Add pmic5_ftsmps520 buck satya priya
2021-03-31 12:05 ` [PATCH V3 2/5] regulator: qcom-rpmh: Add PM7325/PMR735A regulator support satya priya
2021-03-31 18:10   ` Matthias Kaehlcke
2021-03-31 12:05 ` [PATCH V3 3/5] arm64: dts: qcom: sc7280: Add RPMh regulators for sc7280-idp satya priya
2021-03-31 18:30   ` Matthias Kaehlcke
2021-03-31 12:05 ` [PATCH V3 4/5] dt-bindings: regulator: Convert RPMh regulator bindings to YAML satya priya
2021-03-31 12:18   ` Mark Brown
2021-04-01 16:56   ` Rob Herring
2021-03-31 12:05 ` [PATCH V3 5/5] dt-bindings: regulator: Add compatibles for PM7325/PMR735A satya priya
2021-04-01 20:43 ` Mark Brown [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=161730974895.25526.12885475666064429104.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kgunda@codeaurora.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rnayak@codeaurora.org \
    --cc=robh+dt@kernel.org \
    --cc=skakit@codeaurora.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).