All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Viken Dadhaniya <quic_vdadhani@quicinc.com>,
	andersson@kernel.org, konrad.dybcio@linaro.org, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Cc: quic_msavaliy@quicinc.com, quic_anupkulk@quicinc.com
Subject: Re: [PATCH v1] dt-bindings: qcom: geni-se: Rename qcom,geni-se.yaml to qcom,geni-se-qup.yaml
Date: Mon, 24 Feb 2025 11:18:15 +0100	[thread overview]
Message-ID: <ed8f7aee-e5be-453c-b324-e59e90ecee77@kernel.org> (raw)
In-Reply-To: <f3349d2a-7eba-4865-9b58-0b2e7e57cc92@quicinc.com>

On 24/02/2025 09:47, Viken Dadhaniya wrote:
> 
> 
> On 2/21/2025 5:05 PM, Krzysztof Kozlowski wrote:
>> On 21/02/2025 09:54, Viken Dadhaniya wrote:
>>> The qcom,geni-se.yaml file describes the Qualcomm Universal Peripheral
>>> (QUP) wrapper and the common entities required by QUP to run any Serial
>>> Engine (SE) as I2C, SPI, UART, or I3C protocol.
>>>
>>> Rename qcom,geni-se.yaml to qcom,geni-se-qup.yaml to better reflect its
>>> association with QUP (Qualcomm Universal Peripheral) and the compatible
>>> string.
>>>
>>> Signed-off-by: Viken Dadhaniya <quic_vdadhani@quicinc.com>
>>> ---
>>>   .../soc/qcom/{qcom,geni-se.yaml => qcom,geni-se-qup.yaml}       | 2 +-
>>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>>   rename Documentation/devicetree/bindings/soc/qcom/{qcom,geni-se.yaml => qcom,geni-se-qup.yaml} (98%)
>>>
>>
>> That's just churn for no real gain. Not even tested churn.
> 
> That's just churn for no real gain.
> 
> We made this change based on below plan, we think this will be helpful.
> 
> 1. Rename qcom,geni-se.yaml to qcom,geni-se-qup.yaml. Reason at 2 below.

There is no reason 2 at this point. You split your patchsets
incorrectly. At this point this is churn, without gain. No users of this
rename, no benefits.

> 2. Create qcom,geni-se.yaml with shared properties for SE-protocol (spi, 
> i2c, uart) nodes. This will be helpful for the shared schema in the 
> ongoing changes 

Then post it, instead of sending something which makes no sense on its own.


Best regards,
Krzysztof

  reply	other threads:[~2025-02-24 10:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-21  8:54 [PATCH v1] dt-bindings: qcom: geni-se: Rename qcom,geni-se.yaml to qcom,geni-se-qup.yaml Viken Dadhaniya
2025-02-21 10:28 ` Rob Herring (Arm)
2025-02-21 11:35 ` Krzysztof Kozlowski
2025-02-24  8:47   ` Viken Dadhaniya
2025-02-24 10:18     ` Krzysztof Kozlowski [this message]
2025-02-24 13:25       ` Viken Dadhaniya
2025-02-24 13:29         ` Krzysztof Kozlowski
2025-02-25  9:33           ` Viken Dadhaniya
2025-02-25 13:19             ` Krzysztof Kozlowski
2025-02-26  4:19               ` Viken Dadhaniya

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=ed8f7aee-e5be-453c-b324-e59e90ecee77@kernel.org \
    --to=krzk@kernel.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_anupkulk@quicinc.com \
    --cc=quic_msavaliy@quicinc.com \
    --cc=quic_vdadhani@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 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.