From: Krzysztof Kozlowski <krzk@kernel.org>
To: Tingguo Cheng <quic_tingguoc@quicinc.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>
Cc: kernel@quicinc.com, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org, quic_fenglinw@quicinc.com,
quic_tingweiz@quicinc.com
Subject: Re: [PATCH 1/2] dt-bindings: power: qcom,rpmpd: document qcs615 RPMh power domains
Date: Fri, 20 Sep 2024 15:15:22 +0200 [thread overview]
Message-ID: <30458916-90f4-4126-b5b4-a52f580c4fa7@kernel.org> (raw)
In-Reply-To: <20240920-add_qcs615_powerdomains_driver_support-v1-1-8846efaf9454@quicinc.com>
On 20/09/2024 06:08, Tingguo Cheng wrote:
> Add compatible string for the RPMh power domains on qcs615 platform.
>
> Signed-off-by: Tingguo Cheng <quic_tingguoc@quicinc.com>
> ---
> Documentation/devicetree/bindings/power/qcom,rpmpd.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
You sent within 30 minutes two independent patchsets touching the same
part of code, so you knew it will lead to conflicts. I don't get how you
imagine this to be applied. I suggest combining patchsets in such case.
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-09-20 13:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-20 4:08 [PATCH 0/2] Add rpmhpd power domains driver support for QCS615 Tingguo Cheng
2024-09-20 4:08 ` [PATCH 1/2] dt-bindings: power: qcom,rpmpd: document qcs615 RPMh power domains Tingguo Cheng
2024-09-20 13:15 ` Krzysztof Kozlowski [this message]
2024-09-27 12:16 ` Tingguo Cheng
2024-09-27 12:25 ` Krzysztof Kozlowski
2024-09-20 4:08 ` [PATCH 2/2] pmdomain: qcom: rpmhpd: Add qcs615 " Tingguo Cheng
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=30458916-90f4-4126-b5b4-a52f580c4fa7@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@quicinc.com \
--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_fenglinw@quicinc.com \
--cc=quic_tingguoc@quicinc.com \
--cc=quic_tingweiz@quicinc.com \
--cc=robh@kernel.org \
--cc=ulf.hansson@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