From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Kathiravan T <quic_kathirav@quicinc.com>,
agross@kernel.org, andersson@kernel.org,
konrad.dybcio@linaro.org, jassisinghbrar@gmail.com,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 3/3] arm64: dts: qcom: ipq8074: add compatible fallback to mailbox
Date: Tue, 14 Mar 2023 08:08:07 +0100 [thread overview]
Message-ID: <e2d2bbcb-409e-2b13-114f-ee17a3f6c894@linaro.org> (raw)
In-Reply-To: <4deec4ba-a905-6460-1d1c-e5a0abd042fc@linaro.org>
On 14/03/2023 07:45, Krzysztof Kozlowski wrote:
> On 14/03/2023 05:15, Kathiravan T wrote:
>> From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>>
>> IPQ8074 mailbox is compatible with IPQ6018.
>>
>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>> Signed-off-by: Kathiravan T <quic_kathirav@quicinc.com>
>> ---
>> arch/arm64/boot/dts/qcom/ipq8074.dtsi | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> What's this? Not even a dependency for something as it is last patch in
> the series. What's the point?
To be clear - that's a NAK.
Best regards,
Krzysztof
prev parent reply other threads:[~2023-03-14 7:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 4:15 [PATCH 0/3] rework mailbox compatibles for Qualcomm IPQ SoCs Kathiravan T
2023-03-14 4:15 ` [PATCH 1/3] dt-bindings: mailbox: qcom: use fallback for IPQ8074 SoC Kathiravan T
2023-03-14 7:06 ` Krzysztof Kozlowski
2023-03-14 4:15 ` [PATCH 2/3] mailbox: qcom-apcs-ipc: drop the IPQ8074 and IPQ5332 compatible Kathiravan T
2023-03-14 7:07 ` Krzysztof Kozlowski
2023-03-14 4:15 ` [PATCH 3/3] arm64: dts: qcom: ipq8074: add compatible fallback to mailbox Kathiravan T
2023-03-14 6:45 ` Krzysztof Kozlowski
2023-03-14 7:08 ` 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=e2d2bbcb-409e-2b13-114f-ee17a3f6c894@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jassisinghbrar@gmail.com \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_kathirav@quicinc.com \
--cc=robh+dt@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