From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Andy Gross <agross@kernel.org>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: (subset) [PATCH 1/4] dt-bindings: clock: qcom,gcc-msm8996: add more GCC clock sources
Date: Wed, 6 Jul 2022 21:31:07 -0500 [thread overview]
Message-ID: <165716107314.864223.13075882102368205283.b4-ty@linaro.org> (raw)
In-Reply-To: <20220620071936.1558906-2-dmitry.baryshkov@linaro.org>
On Mon, 20 Jun 2022 10:19:33 +0300, Dmitry Baryshkov wrote:
> Add additional GCC clock sources. This includes PCIe and USB PIPE and
> UFS symbol clocks.
>
>
Applied, thanks!
[1/4] dt-bindings: clock: qcom,gcc-msm8996: add more GCC clock sources
commit: 2b4e75a7a7c8d3531a40ebb103b92f88ff693f79
Best regards,
--
Bjorn Andersson <bjorn.andersson@linaro.org>
next prev parent reply other threads:[~2022-07-07 2:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 7:19 [PATCH 0/4] arm64: dts: qcom: msm8996: add missing clock sources Dmitry Baryshkov
2022-06-20 7:19 ` [PATCH 1/4] dt-bindings: clock: qcom,gcc-msm8996: add more GCC " Dmitry Baryshkov
2022-06-20 11:22 ` Krzysztof Kozlowski
2022-07-07 2:31 ` Bjorn Andersson [this message]
2022-06-20 7:19 ` [PATCH 2/4] arm64: dts: qcom: msm8996: correct #clock-cells for QMP PHY nodes Dmitry Baryshkov
2022-06-20 7:19 ` [PATCH 3/4] arm64: dts: qcom: msm8996: add GCC's optional clock sources Dmitry Baryshkov
2022-06-20 11:24 ` Krzysztof Kozlowski
2022-06-20 11:27 ` Dmitry Baryshkov
2022-06-20 12:35 ` Krzysztof Kozlowski
2022-06-20 7:19 ` [PATCH 4/4] arm64: dts: qcom: msm8996: add xo clock source to rpmcc Dmitry Baryshkov
2022-07-07 2:31 ` (subset) [PATCH 0/4] arm64: dts: qcom: msm8996: add missing clock sources Bjorn Andersson
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=165716107314.864223.13075882102368205283.b4-ty@linaro.org \
--to=bjorn.andersson@linaro.org \
--cc=agross@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=robh+dt@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.