From: Krzysztof Kozlowski <krzk@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Bjorn Andersson <andersson@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Taniya Das <quic_tdas@quicinc.com>,
Robert Marko <robimarko@gmail.com>,
Konrad Dybcio <konrad.dybcio@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 09/10] arm64: dts: qcom: ipq6018: fix GCC node name
Date: Wed, 29 May 2024 09:39:46 +0200 [thread overview]
Message-ID: <40781e75-26ea-4d32-a63c-89a8d1c2d92f@kernel.org> (raw)
In-Reply-To: <20240528-qcom-gdscs-v1-9-03cf1b102a4f@linaro.org>
On 28/05/2024 22:43, Dmitry Baryshkov wrote:
> Device nodes should have generic names. Use 'clock-controller@' as a GCC
> node name instead of a non-generic 'gcc@'.
>
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> ---
> arch/arm64/boot/dts/qcom/ipq6018.dtsi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-05-29 7:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 20:43 [PATCH 00/10] dt-bindings: clock: qcom,gcc: handle the controllers without power domains Dmitry Baryshkov
2024-05-28 20:43 ` [PATCH 01/10] dt-bindings: clock: qcom: split the non-PD schema for GCC Dmitry Baryshkov
2024-05-29 7:34 ` Krzysztof Kozlowski
2024-05-29 7:58 ` Dmitry Baryshkov
2024-05-29 12:30 ` Krzysztof Kozlowski
2024-05-28 20:43 ` [PATCH 02/10] dt-bindings: clock: qcom,gcc-apq8064: use non-power-domain version of GCC schema Dmitry Baryshkov
2024-05-28 22:02 ` Rob Herring (Arm)
2024-05-28 20:43 ` [PATCH 03/10] dt-bindings: clock: qcom,gcc-msm8660: " Dmitry Baryshkov
2024-05-28 22:02 ` Rob Herring (Arm)
2024-05-28 20:43 ` [PATCH 04/10] dt-bindings: clock: qcom,gcc-ipq6018: " Dmitry Baryshkov
2024-05-28 22:02 ` Rob Herring (Arm)
2024-05-28 20:43 ` [PATCH 05/10] dt-bindings: clock: qcom,gcc-nopd.yaml: force node name Dmitry Baryshkov
2024-05-29 7:39 ` Krzysztof Kozlowski
2024-05-29 7:40 ` Dmitry Baryshkov
2024-05-28 20:43 ` [PATCH 06/10] ARM: dts: qcom: apq8064: drop #power-domain-cells property of GCC Dmitry Baryshkov
2024-05-28 20:43 ` [PATCH 07/10] ARM: dts: qcom: msm8660: " Dmitry Baryshkov
2024-05-28 20:43 ` [PATCH 08/10] ARM: dts: qcom: msm8960: " Dmitry Baryshkov
2024-05-28 20:43 ` [PATCH 09/10] arm64: dts: qcom: ipq6018: fix GCC node name Dmitry Baryshkov
2024-05-29 7:39 ` Krzysztof Kozlowski [this message]
2024-05-28 20:43 ` [PATCH 10/10] arm64: dts: qcom: ipq8074: " Dmitry Baryshkov
2024-05-29 7:39 ` Krzysztof Kozlowski
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=40781e75-26ea-4d32-a63c-89a8d1c2d92f@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzk+dt@kernel.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_tdas@quicinc.com \
--cc=robh@kernel.org \
--cc=robimarko@gmail.com \
--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).