All of lore.kernel.org
 help / color / mirror / Atom feed
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 2/3] mailbox: qcom-apcs-ipc: drop the IPQ8074 and IPQ5332 compatible
Date: Tue, 14 Mar 2023 08:07:44 +0100	[thread overview]
Message-ID: <294488c6-098b-cefc-7c56-cb0d7beeb4e7@linaro.org> (raw)
In-Reply-To: <20230314041515.15883-3-quic_kathirav@quicinc.com>

On 14/03/2023 05:15, Kathiravan T wrote:
> Since the IPQ8074 and IPQ5332 mailbox are compatible with IPQ6018, we can
> use the compatible fallback to IPQ6018. With that, we can drop the
> IPQ8074 and IPQ5332 compatible references, as well we don't bloat the
> of_device_id table.
> 
> Suggested-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>

NAK. Breaks ABI and duplicates what I already sent (which you saw since
you took my patches from my thread).

https://lore.kernel.org/all/20230202161856.385825-4-krzysztof.kozlowski@linaro.org/


Best regards,
Krzysztof


  reply	other threads:[~2023-03-14  7:07 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 [this message]
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

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=294488c6-098b-cefc-7c56-cb0d7beeb4e7@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.