From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Gokul Sriram P <quic_gokulsri@quicinc.com>,
dmitry.baryshkov@linaro.org, agross@kernel.org,
andersson@kernel.org, konrad.dybcio@linaro.org,
mturquette@baylibre.com, sboyd@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, jassisinghbrar@gmail.com,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: quic_varada@quicinc.com, quic_srichara@quicinc.com
Subject: Re: [PATCH V3 0/3] Add APSS clock driver support for IPQ5018
Date: Fri, 27 Oct 2023 10:09:58 +0200 [thread overview]
Message-ID: <063acbcc-81db-457e-bc4d-c572c8e4b10f@linaro.org> (raw)
In-Reply-To: <544f270e-ad62-6b15-13e6-72ca32d46d31@quicinc.com>
On 27/10/2023 10:02, Gokul Sriram P wrote:
> Hi everyone, a gentle remainder to review and acknowledge the change.
Really everyone? So what do you miss from me? Any why do you think that
I did not perform my duties?
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-10-27 8:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 10:28 [PATCH V3 0/3] Add APSS clock driver support for IPQ5018 Gokul Sriram Palanisamy
2023-09-25 10:28 ` [PATCH V3 1/3] dt-bindings: clock: qcom,a53pll: add IPQ5018 compatible Gokul Sriram Palanisamy
2023-09-25 10:28 ` [PATCH V3 2/3] clk: qcom: apss-ipq-pll: add support for IPQ5018 Gokul Sriram Palanisamy
2023-09-25 10:28 ` [PATCH V3 3/3] arm64: dts: qcom: ipq5018: enable the CPUFreq support Gokul Sriram Palanisamy
2023-09-25 10:57 ` Krzysztof Kozlowski
2023-10-27 8:02 ` [PATCH V3 0/3] Add APSS clock driver support for IPQ5018 Gokul Sriram P
2023-10-27 8:09 ` Krzysztof Kozlowski [this message]
2023-12-03 4:54 ` (subset) " 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=063acbcc-81db-457e-bc4d-c572c8e4b10f@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=jassisinghbrar@gmail.com \
--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=quic_gokulsri@quicinc.com \
--cc=quic_srichara@quicinc.com \
--cc=quic_varada@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@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 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).