From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Richard Acayan <mailingradian@gmail.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Georgi Djakov <djakov@kernel.org>,
Manivannan Sadhasivam <mani@kernel.org>,
Sibi Sankar <quic_sibis@quicinc.com>,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 3/3] arm64: dts: qcom: sdm670: add specific cpufreq compatible
Date: Wed, 16 Aug 2023 07:38:10 +0200 [thread overview]
Message-ID: <34ae2658-f6eb-1ad6-5d59-35ff5ad3a97f@linaro.org> (raw)
In-Reply-To: <20230815223108.306018-8-mailingradian@gmail.com>
On 16/08/2023 00:31, Richard Acayan wrote:
> The bindings for the CPU frequency scaling driver require a specific
> compatible for the SoC. Add the compatible.
>
> Fixes: 0c665213d126 ("arm64: dts: qcom: sdm670: add cpu frequency scaling")
> Signed-off-by: Richard Acayan <mailingradian@gmail.com>
There was no such compatible in your series, so backporting only this is
not enough.
Best regards,
Krzysztof
prev parent reply other threads:[~2023-08-16 5:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 22:31 [PATCH 0/3] SDM670 CPU frequency scaling: dtschema fixes Richard Acayan
2023-08-15 22:31 ` [PATCH 1/3] dt-bindings: interconnect: add SDM670 OSM L3 compatible Richard Acayan
2023-08-16 23:03 ` Richard Acayan
2023-08-15 22:31 ` [PATCH 2/3] dt-bindings: cpufreq: cpufreq-qcom-hw: add SDM670 compatible Richard Acayan
2023-08-16 5:36 ` Krzysztof Kozlowski
2023-08-15 22:31 ` [PATCH 3/3] arm64: dts: qcom: sdm670: add specific cpufreq compatible Richard Acayan
2023-08-16 5:38 ` Krzysztof Kozlowski [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=34ae2658-f6eb-1ad6-5d59-35ff5ad3a97f@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=djakov@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mailingradian@gmail.com \
--cc=mani@kernel.org \
--cc=quic_sibis@quicinc.com \
--cc=rafael@kernel.org \
--cc=robh+dt@kernel.org \
--cc=viresh.kumar@linaro.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).