From: Bjorn Andersson <andersson@kernel.org>
To: mailingradian@gmail.com, linux-arm-msm@vger.kernel.org
Cc: agross@kernel.org, mturquette@baylibre.com, sboyd@kernel.org,
jo@jsfamily.in, konrad.dybcio@somainline.org,
linux-clk@vger.kernel.org, robh+dt@kernel.org,
caleb@connolly.tech, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
krzysztof.kozlowski+dt@linaro.org
Subject: Re: [PATCH v4 0/3] SDM670 Global Clocks
Date: Wed, 14 Sep 2022 22:36:59 -0500 [thread overview]
Message-ID: <166321302049.788007.6905629348240646404.b4-ty@kernel.org> (raw)
In-Reply-To: <20220914013922.198778-1-mailingradian@gmail.com>
On Tue, 13 Sep 2022 21:39:19 -0400, Richard Acayan wrote:
> Changes since v3:
> - rebase onto next-20220913
> - accumulate review tags
>
> Changes since v2:
> - drop GCC_SDCC1_BCR reset
> - reorder gcc-sdm845 and gcc-sdm670 if statements in bindings
> - add space
> - accumulate review tags
>
> [...]
Applied, thanks!
[1/3] dt-bindings: clock: gcc-sdm845: add sdm670 global clocks
commit: 657e9326658c1c570eb1e8fd122a4a7936433673
[2/3] clk: qcom: gcc-sdm845: use device tree match data
commit: 8e90216d2db99f0b883be3b40d5b581437dc4a5d
[3/3] clk: qcom: gcc-sdm845: add sdm670 global clock data
commit: ae66b1fe48e2dd91229f2b8f25295bce629382d0
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2022-09-15 3:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 1:39 [PATCH v4 0/3] SDM670 Global Clocks Richard Acayan
2022-09-14 1:39 ` [PATCH v4 1/3] dt-bindings: clock: gcc-sdm845: add sdm670 global clocks Richard Acayan
2022-09-14 1:39 ` [PATCH v4 2/3] clk: qcom: gcc-sdm845: use device tree match data Richard Acayan
2022-09-14 1:39 ` [PATCH v4 3/3] clk: qcom: gcc-sdm845: add sdm670 global clock data Richard Acayan
2022-09-15 3:36 ` Bjorn Andersson [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=166321302049.788007.6905629348240646404.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=agross@kernel.org \
--cc=caleb@connolly.tech \
--cc=devicetree@vger.kernel.org \
--cc=jo@jsfamily.in \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mailingradian@gmail.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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