From: Jun Guo <jun.guo@cixtech.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
peter.chen@cixtech.com, fugang.duan@cixtech.com, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, vkoul@kernel.org,
ychuang3@nuvoton.com, schung@nuvoton.com, robin.murphy@arm.com
Cc: dmaengine@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, cix-kernel-upstream@cixtech.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/3] dt-bindings: dma: arm-dma350: update DT binding docs
Date: Tue, 18 Nov 2025 09:37:01 +0800 [thread overview]
Message-ID: <f32810d7-64a1-4d29-bdf0-04b9930faf15@cixtech.com> (raw)
In-Reply-To: <7df26091-97be-4494-8140-5e2ca54780ea@kernel.org>
On 11/17/2025 9:29 PM, Krzysztof Kozlowski wrote:
> On 17/11/2025 13:51, Jun Guo wrote:
>> On 11/17/2025 3:13 PM, Krzysztof Kozlowski wrote:
>>> EXTERNAL EMAIL
>>>
>>> On 17/11/2025 08:11, Krzysztof Kozlowski wrote:
>>>> On 17/11/2025 08:07, Jun Guo wrote:
>>>>> On 11/17/2025 2:11 PM, Krzysztof Kozlowski wrote:
>>>>>> On 17/11/2025 02:59, Jun Guo wrote:
>>>>>>> - Add new compatible strings to the DT binding documents to support
>>>>>> This is not a list.
>>>>>>
>>>>>> Also, subject is completely redundant. Everything is an update. Why are
>>>>>> you repeating DT binding docs?
>>>>>>
>>>>> Thank you. I will incorporate your feedback in the next version.>> cix
>>>>> sky1 SoC.
>>>>>>> Signed-off-by: Jun Guo<jun.guo@cixtech.com>
>>>>>>> ---
>>>>>> You just broke all existing platforms. Please test your code properly.
>>>>> The patch includes proper checks. Since this platform is the first user
>>>> Nah, tests are here incomplete - look at the binding and DTS users...
>>>> nothing there, so you cannot test it.
>>>>
>>>>> of the driver in the current codebase, the change won't affect other
>>>>> platforms.
>>>> NAK, and you keep pushing... I just told you it will break everyone,
>>>> which is obvious from the diff.
>>> But if that was intentional change of ABI, then could be fine, but you
>>> must provide in commit msg proper detailed rationale WHY you are
>>> changing ABI and WHAT is the ABI impact of that change.
>>>
>> I'm not entirely sure if I fully grasped your point, but I also
>> identified the potential issue. I've reworked the patch to accommodate
>> both the default DTS case with a single compatible string and the
>> scenario where platform-specific compatible strings need to be added.
>> Could you please review it again and confirm if this aligns with your
>> intent?
>>
>> properties:
>> compatible:
>> contains:
> Which example uses such syntax?
>
>> enum:
>> - cix,sky1-dma-350
>> - arm,dma-350
> It's completely different than previous, so I don't know what you want
> to achieve, but maybe you wanted to explain lack of compatibility in the
> commit msg. Anyway, send proper patches with proper justification (and
> for above would really need to be proper).
>
OK.Thank you for your prompt reply.> Best regards,
> Krzysztof
Best regards,
Jun
next prev parent reply other threads:[~2025-11-18 1:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 1:59 [PATCH 0/3] dmaengine: arm-dma350: add support for shared interrupt mode Jun Guo
2025-11-17 1:59 ` [PATCH 1/3] dt-bindings: dma: arm-dma350: update DT binding docs Jun Guo
2025-11-17 6:11 ` Krzysztof Kozlowski
2025-11-17 7:07 ` Jun Guo
2025-11-17 7:11 ` Krzysztof Kozlowski
2025-11-17 7:13 ` Krzysztof Kozlowski
2025-11-17 12:51 ` Jun Guo
2025-11-17 13:29 ` Krzysztof Kozlowski
2025-11-18 1:37 ` Jun Guo [this message]
2025-11-17 1:59 ` [PATCH 2/3] dma: arm-dma350: add support for shared interrupt mode Jun Guo
2025-11-17 6:13 ` Krzysztof Kozlowski
2025-11-17 7:18 ` Jun Guo
2025-11-17 11:37 ` Jun Guo
2025-11-17 11:44 ` Krzysztof Kozlowski
2025-11-17 11:52 ` Jun Guo
2025-11-17 11:32 ` Robin Murphy
2025-11-17 11:57 ` Jun Guo
2025-11-17 1:59 ` [PATCH 3/3] arm64: dts: cix: add DT nodes for DMA Jun Guo
2025-11-17 6:14 ` Krzysztof Kozlowski
2025-11-17 7:08 ` Jun Guo
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=f32810d7-64a1-4d29-bdf0-04b9930faf15@cixtech.com \
--to=jun.guo@cixtech.com \
--cc=cix-kernel-upstream@cixtech.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=fugang.duan@cixtech.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.chen@cixtech.com \
--cc=robh@kernel.org \
--cc=robin.murphy@arm.com \
--cc=schung@nuvoton.com \
--cc=vkoul@kernel.org \
--cc=ychuang3@nuvoton.com \
/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
all inboxes | Powered by JetHome®