From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jun Guo <jun.guo@cixtech.com>, Peter Chen <peter.chen@cixtech.com>
Cc: 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, Frank.Li@kernel.org,
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 v3 1/3] dt-bindings: dma: arm-dma350: document generic and combined IRQ topologies
Date: Mon, 23 Mar 2026 08:27:00 +0100 [thread overview]
Message-ID: <7967caff-101a-461a-bc61-aeb8fc8f04b1@kernel.org> (raw)
In-Reply-To: <dd6ee455-7bba-4734-be84-a7db097754c6@cixtech.com>
On 23/03/2026 03:09, Jun Guo wrote:
> Hi Krzysztof,
>
> On 3/20/2026 6:04 PM, Krzysztof Kozlowski wrote:
>> EXTERNAL EMAIL
>>
>> On 20/03/2026 10:58, Peter Chen wrote:
>>> On 26-03-20 10:43:10, Krzysztof Kozlowski wrote:
>>>> EXTERNAL EMAIL
>>>>
>>>> On 20/03/2026 10:38, Peter Chen wrote:
>>>>> On 26-03-20 10:12:53, Krzysztof Kozlowski wrote:
>>>>>> EXTERNAL EMAIL
>>>>>>
>>>>>> On Thu, Mar 19, 2026 at 06:17:21PM +0800, Jun Guo wrote:
>>>>>>> Update the DMA-350 DT binding to match the current driver behavior.
>>>>>>>
>>>>>>> Allow both:
>>>>>>> - "arm,dma-350" as the generic compatible, and
>>>>>>> - "cix,sky1-dma-350", "arm,dma-350" for SoC-specific fallback usage.
>>>>>>>
>>>>>>> Also document interrupt topology variants supported by hardware
>>>>>>> integration:
>>>>>>> - one combined interrupt for all channels, or
>>>>>>> - one interrupt per channel (up to 8 channels).
>>>>>>>
>>>>>>> This patch is Assisted-by: Cursor: GPT-5.3 Codex.
>>>>>>
>>>>>> Wrong tag, please read carefully the guideline before using LLM tools.
>>>>>>
>>>>>
>>>>> Hi Krzysztof,
>>>>>
>>>>> It is the trade off for coding-assistants.rst suggestion and
>>>>> passing checkpatch.pl. Currently, checkpatch.pl reports the
>>>>> error for tag without email address. So we choose to add tag
>>>>> description at patch context.
>>>>
>>>> You still have to use correct tag.
>>>
>>> You mean even checkpatch.pl reports below error, we still add it
>>> "Assisted-by: Cursor: GPT-5.3 Codex" as tag?
>>
>> Yes, after fixing the contents (that's not entirely correct format I
>> think). Hopefully someone will fix checkpatch one day...
> I cannot find any commit records referencing AI via "Co-developed-by" in
> the latest kernel GitHub repository, and I also cannot locate any text
> describing the correct way to cite AI in the submitting-patches.rst
> file. In this case, how can I confirm the current correct format?
If you do not want to read coding with assistant guideline and follow
its words, then please don't send code created with such tools. Do you
even have full copyrights to send it here? What license was used by the
tool to generate you this code?
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-03-23 7:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 10:17 [PATCH v3 0/3] dmaengine: arm-dma350: support combined IRQ topology Jun Guo
2026-03-19 10:17 ` [PATCH v3 1/3] dt-bindings: dma: arm-dma350: document generic and combined IRQ topologies Jun Guo
2026-03-20 9:12 ` Krzysztof Kozlowski
2026-03-20 9:38 ` Peter Chen
2026-03-20 9:43 ` Krzysztof Kozlowski
2026-03-20 9:58 ` Peter Chen
2026-03-20 10:04 ` Krzysztof Kozlowski
2026-03-23 2:09 ` Jun Guo
2026-03-23 7:27 ` Krzysztof Kozlowski [this message]
2026-03-23 7:51 ` Jun Guo
2026-03-20 10:28 ` Jun Guo
2026-03-20 13:12 ` Krzysztof Kozlowski
2026-03-21 8:20 ` Jun Guo
2026-03-19 10:17 ` [PATCH v3 2/3] dma: arm-dma350: support combined IRQ mode with runtime IRQ topology detection Jun Guo
2026-03-19 10:17 ` [PATCH v3 3/3] arm64: dts: cix: add DT nodes for DMA Jun Guo
2026-03-20 9:13 ` Krzysztof Kozlowski
2026-03-20 10: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=7967caff-101a-461a-bc61-aeb8fc8f04b1@kernel.org \
--to=krzk@kernel.org \
--cc=Frank.Li@kernel.org \
--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=jun.guo@cixtech.com \
--cc=krzk+dt@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