From: Bjorn Andersson <andersson@kernel.org>
To: linux-arm-msm@vger.kernel.org, Rayyan Ansari <rayyan@ansari.sh>
Cc: linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Andy Gross <agross@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Stephen Boyd <sboyd@kernel.org>,
Michael Turquette <mturquette@baylibre.com>
Subject: Re: (subset) [PATCH v4 0/3] Add XO clocks for MSM8226/MSM8974
Date: Wed, 15 Mar 2023 20:21:05 -0700 [thread overview]
Message-ID: <167893686408.303819.4516059046726594416.b4-ty@kernel.org> (raw)
In-Reply-To: <20230121192540.9177-1-rayyan@ansari.sh>
On Sat, 21 Jan 2023 19:25:37 +0000, Rayyan Ansari wrote:
> Changes since v3:
> - Put the rpmcc.h include back in
>
> Rayyan Ansari (3):
> clk: qcom: smd: Add XO RPM clocks for MSM8226/MSM8974
> ARM: dts: qcom: msm8226: add clocks and clock-names to GCC node
> ARM: dts: qcom: msm8974: add correct XO clock source to GCC node
>
> [...]
Applied, thanks!
[2/3] ARM: dts: qcom: msm8226: add clocks and clock-names to GCC node
commit: d4b2c596fe5cb62560ce5a1442d8f64ec1ee716e
[3/3] ARM: dts: qcom: msm8974: add correct XO clock source to GCC node
commit: 17c5ee1914dc8c4f42cab7a5beb2dc91aef0f873
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2023-03-16 3:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-21 19:25 Rayyan Ansari
2023-01-21 19:25 ` [PATCH v4 1/3] clk: qcom: smd: Add XO RPM " Rayyan Ansari
2023-01-23 16:50 ` Konrad Dybcio
2023-01-25 20:58 ` Stephen Boyd
2023-01-25 22:25 ` Rayyan Ansari
2023-01-25 23:00 ` Stephen Boyd
2023-01-25 23:33 ` Konrad Dybcio
2023-01-27 8:18 ` Luca Weiss
2023-01-21 19:25 ` [PATCH v4 2/3] ARM: dts: qcom: msm8226: add clocks and clock-names to GCC node Rayyan Ansari
2023-01-23 16:54 ` Konrad Dybcio
2023-01-21 19:25 ` [PATCH v4 3/3] ARM: dts: qcom: msm8974: add correct XO clock source " Rayyan Ansari
2023-03-16 3:21 ` 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=167893686408.303819.4516059046726594416.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=agross@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.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=mturquette@baylibre.com \
--cc=rayyan@ansari.sh \
--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
all inboxes | Powered by JetHome®