From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Christian Marangi <ansuelsmth@gmail.com>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>,
Andy Gross <agross@kernel.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/5] ARM: DTS: qcom: fix dtbs_check warning with new rpmcc clocks
Date: Wed, 6 Jul 2022 17:07:12 +0200 [thread overview]
Message-ID: <bcb64218-2d2b-2f6b-dc79-303bac8c3bd3@linaro.org> (raw)
In-Reply-To: <62c565dc.1c69fb81.a4566.e9b2@mx.google.com>
On 06/07/2022 12:20, Christian Marangi wrote:
> On Wed, Jul 06, 2022 at 09:44:04AM +0200, Krzysztof Kozlowski wrote:
>> On 05/07/2022 22:28, Christian Marangi wrote:
>>> Fix dtbs_check warning for new rpmcc Documentation changes and add the
>>> required clocks.
>>
>> There is no warning in the kernel, right? So the commit is not correct.
>>
>
> Oh ok, the warning is generated by the new Documentation.
Patches, especially DTS, might go via different trees, so the moment DTS
is applied there might be no such warning.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-07-06 15:07 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 20:28 [PATCH 0/5] clk: qcom: Drop use of pxo/cxo_board for rpm devices Christian Marangi
2022-07-05 20:28 ` [PATCH 1/5] dt-bindings: clock: fix wrong clock documentation for qcom,rpmcc Christian Marangi
2022-07-06 7:43 ` Krzysztof Kozlowski
2022-07-06 8:23 ` Dmitry Baryshkov
2022-07-06 10:19 ` Christian Marangi
2022-07-06 11:58 ` Dmitry Baryshkov
2022-07-05 20:28 ` [PATCH 2/5] ARM: DTS: qcom: fix dtbs_check warning with new rpmcc clocks Christian Marangi
2022-07-06 7:35 ` Dmitry Baryshkov
2022-07-06 7:44 ` Krzysztof Kozlowski
2022-07-06 10:20 ` Christian Marangi
2022-07-06 15:07 ` Krzysztof Kozlowski [this message]
2022-07-06 19:10 ` Christian Marangi
2022-07-06 20:09 ` Krzysztof Kozlowski
2022-07-06 20:38 ` Christian Marangi
2022-07-05 20:28 ` [PATCH 3/5] clk: qcom: clk-rpm: convert to parent_data API Christian Marangi
2022-07-06 8:27 ` Dmitry Baryshkov
2022-07-06 10:21 ` Christian Marangi
2022-07-06 13:26 ` Konrad Dybcio
2022-07-06 13:16 ` Christian Marangi
2022-07-05 20:28 ` [PATCH 4/5] ARM: dts: qcom: add pxo/cxo clock-output-names for ipq8064 Christian Marangi
2022-07-06 8:29 ` Dmitry Baryshkov
2022-07-06 10:22 ` Christian Marangi
2022-07-06 13:24 ` Konrad Dybcio
2022-07-05 20:28 ` [PATCH 5/5] clk: qcom: gcc-ipq806x: remove cc_register_board for pxo and cxo Christian Marangi
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=bcb64218-2d2b-2f6b-dc79-303bac8c3bd3@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=ansuelsmth@gmail.com \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@somainline.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=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).