From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Tengfei Fan <quic_tengfan@quicinc.com>,
Georgi Djakov <djakov@kernel.org>, Rob Herring <robh@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>
Cc: kernel@quicinc.com, linux-arm-msm@vger.kernel.org,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: interconnect: qcom-bwmon: Document SA8775p bwmon compatibles
Date: Wed, 31 Jul 2024 11:23:35 +0200 [thread overview]
Message-ID: <1e78eeb9-3280-45ea-9d21-92efd939efe7@linaro.org> (raw)
In-Reply-To: <20240730-add_sa8775p_bwmon-v1-1-f4f878da29ae@quicinc.com>
On 30/07/2024 09:16, Tengfei Fan wrote:
> Document the compatibles used to describe the bwmons present on the
> SA8775p platform.
>
> Signed-off-by: Tengfei Fan <quic_tengfan@quicinc.com>
> ---
> Documentation/devicetree/bindings/interconnect/qcom,msm8998-bwmon.yaml | 2 ++
> 1 file changed, 2 insertions(+)
I admit I don't know what to do with all these sa8775p patches. I am
afraid now you say these are valid but in half a year this will change.
If I give Ack, I feel like I am agreeing to such approach, which I do not.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-07-31 9:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-30 7:16 [PATCH 0/2] arm64: qcom: Add BWMON support for SA8775p Tengfei Fan
2024-07-30 7:16 ` [PATCH 1/2] dt-bindings: interconnect: qcom-bwmon: Document SA8775p bwmon compatibles Tengfei Fan
2024-07-31 9:23 ` Krzysztof Kozlowski [this message]
2024-07-31 19:30 ` Trilok Soni
2024-08-01 7:51 ` Krzysztof Kozlowski
2024-07-30 7:16 ` [PATCH 2/2] arm64: dts: qcom: sa8775p: Add CPU and LLCC BWMON Tengfei Fan
2024-08-15 20:40 ` (subset) [PATCH 0/2] arm64: qcom: Add BWMON support for SA8775p 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=1e78eeb9-3280-45ea-9d21-92efd939efe7@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=djakov@kernel.org \
--cc=kernel@quicinc.com \
--cc=konrad.dybcio@linaro.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=quic_tengfan@quicinc.com \
--cc=robh@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).