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.
Signed-off-by: Jun Guo <jun.guo@cixtech.com>
Link: https://lore.kernel.org/r/20251216123026.3519923-2-jun.guo@cixtech.com
---
.../devicetree/bindings/dma/arm,dma-350.yaml | 31 +++++++++++++------
1 file changed, 21 insertions(+), 10 deletions(-)
diff --git a/Documentation/devicetree/bindings/dma/arm,dma-350.yaml b/Documentation/devicetree/bindings/dma/arm,dma-350.yaml
index 429f682f15d8..3639ce0d5054 100644
--- a/Documentation/devicetree/bindings/dma/arm,dma-350.yaml
+++ b/Documentation/devicetree/bindings/dma/arm,dma-350.yaml
@@ -14,7 +14,11 @@ allOf:
properties:
compatible:
- const: arm,dma-350
+ oneOf:
+ - const: arm,dma-350
+ - items:
+ - const: cix,sky1-dma-350
+ - const: arm,dma-350
reg:
items:
@@ -22,15 +26,22 @@ properties:
interrupts:
minItems: 1
- items:
- - description: Channel 0 interrupt
- - description: Channel 1 interrupt
- - description: Channel 2 interrupt
- - description: Channel 3 interrupt
- - description: Channel 4 interrupt
- - description: Channel 5 interrupt
- - description: Channel 6 interrupt
- - description: Channel 7 interrupt
+ maxItems: 8
+ description: |
+ The DMA controller may be configured with separate interrupts for each channel,
+ or with a single combined interrupt for all channels, depending on the SoC integration.
+ oneOf:
+ - items:
+ - description: Channel 0 interrupt
+ - description: Channel 1 interrupt
+ - description: Channel 2 interrupt
+ - description: Channel 3 interrupt
+ - description: Channel 4 interrupt
+ - description: Channel 5 interrupt
+ - description: Channel 6 interrupt
+ - description: Channel 7 interrupt
+ - items:
+ - description: Combined interrupt shared by all channels
"#dma-cells":
const: 1
--
2.34.1On 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. > > Signed-off-by: Jun Guo <jun.guo@cixtech.com> > Link: https://lore.kernel.org/r/20251216123026.3519923-2-jun.guo@cixtech.com What does this express? Changelog link? Then keep it in the changelog --- part. > --- > .../devicetree/bindings/dma/arm,dma-350.yaml | 31 +++++++++++++------ > 1 file changed, 21 insertions(+), 10 deletions(-) > > diff --git a/Documentation/devicetree/bindings/dma/arm,dma-350.yaml b/Documentation/devicetree/bindings/dma/arm,dma-350.yaml > index 429f682f15d8..3639ce0d5054 100644 > --- a/Documentation/devicetree/bindings/dma/arm,dma-350.yaml > +++ b/Documentation/devicetree/bindings/dma/arm,dma-350.yaml > @@ -14,7 +14,11 @@ allOf: > > properties: > compatible: > - const: arm,dma-350 > + oneOf: > + - const: arm,dma-350 > + - items: > + - const: cix,sky1-dma-350 > + - const: arm,dma-350 > > reg: > items: > @@ -22,15 +26,22 @@ properties: > > interrupts: > minItems: 1 > - items: > - - description: Channel 0 interrupt > - - description: Channel 1 interrupt > - - description: Channel 2 interrupt > - - description: Channel 3 interrupt > - - description: Channel 4 interrupt > - - description: Channel 5 interrupt > - - description: Channel 6 interrupt > - - description: Channel 7 interrupt > + maxItems: 8 > + description: | > + The DMA controller may be configured with separate interrupts for each channel, > + or with a single combined interrupt for all channels, depending on the SoC integration. And more important - you must review the LLM microslop output before posting and adjust it to Linux kernel coding style. Don't send unredacted tool output. Best regards, Krzysztof
On 3/20/2026 5:12 PM, 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.
Okay. I will temporarily disregard the check patch warnings in the next
version and correct the format of the AI-generated tag.
>
>>
>> Signed-off-by: Jun Guo <jun.guo@cixtech.com>
>> Link: https://lore.kernel.org/r/20251216123026.3519923-2-jun.guo@cixtech.com
>
> What does this express? Changelog link? Then keep it in the changelog
> --- part.
Okay, I'll address this in the next version of the patch.
>
>
>> ---
>> .../devicetree/bindings/dma/arm,dma-350.yaml | 31 +++++++++++++------
>> 1 file changed, 21 insertions(+), 10 deletions(-)
>>
>> diff --git a/Documentation/devicetree/bindings/dma/arm,dma-350.yaml b/Documentation/devicetree/bindings/dma/arm,dma-350.yaml
>> index 429f682f15d8..3639ce0d5054 100644
>> --- a/Documentation/devicetree/bindings/dma/arm,dma-350.yaml
>> +++ b/Documentation/devicetree/bindings/dma/arm,dma-350.yaml
>> @@ -14,7 +14,11 @@ allOf:
>>
>> properties:
>> compatible:
>> - const: arm,dma-350
>> + oneOf:
>> + - const: arm,dma-350
>> + - items:
>> + - const: cix,sky1-dma-350
>> + - const: arm,dma-350
>>
>> reg:
>> items:
>> @@ -22,15 +26,22 @@ properties:
>>
>> interrupts:
>> minItems: 1
>> - items:
>> - - description: Channel 0 interrupt
>> - - description: Channel 1 interrupt
>> - - description: Channel 2 interrupt
>> - - description: Channel 3 interrupt
>> - - description: Channel 4 interrupt
>> - - description: Channel 5 interrupt
>> - - description: Channel 6 interrupt
>> - - description: Channel 7 interrupt
>> + maxItems: 8
>> + description: |
>> + The DMA controller may be configured with separate interrupts for each channel,
>> + or with a single combined interrupt for all channels, depending on the SoC integration.
>
> And more important - you must review the LLM microslop output before
> posting and adjust it to Linux kernel coding style. Don't send
> unredacted tool output.
>
Actually, this part of the description was not AI-generated. However,
I’d like to confirm the issue you mentioned: are you saying that this
description is written too verbosely?
Then, do you think there are still issues with the revised version?
interrupts:
minItems: 1
maxItems: 8
description:
Either one interrupt per channel (8 interrupts), or one
combined interrupt for all channels.
> Best regards,
> Krzysztof
>
On 20/03/2026 11:28, Jun Guo wrote: >>> + description: | >>> + The DMA controller may be configured with separate interrupts for each channel, >>> + or with a single combined interrupt for all channels, depending on the SoC integration. >> >> And more important - you must review the LLM microslop output before >> posting and adjust it to Linux kernel coding style. Don't send >> unredacted tool output. >> > Actually, this part of the description was not AI-generated. However, > I’d like to confirm the issue you mentioned: are you saying that this > description is written too verbosely? > Then, do you think there are still issues with the revised version? > interrupts: > minItems: 1 > maxItems: 8 > description: > Either one interrupt per channel (8 interrupts), or one > combined interrupt for all channels. No, it is not wrapped according to Linux coding style. Please wrap code according to the preferred limit expressed in Kernel coding style (checkpatch is not a coding style description, but only a tool). However don't wrap blindly (see Kernel coding style). Best regards, Krzysztof
On 3/20/2026 9:12 PM, Krzysztof Kozlowski wrote: > EXTERNAL EMAIL > > On 20/03/2026 11:28, Jun Guo wrote: >>>> + description: | >>>> + The DMA controller may be configured with separate interrupts for each channel, >>>> + or with a single combined interrupt for all channels, depending on the SoC integration. >>> >>> And more important - you must review the LLM microslop output before >>> posting and adjust it to Linux kernel coding style. Don't send >>> unredacted tool output. >>> >> Actually, this part of the description was not AI-generated. However, >> I’d like to confirm the issue you mentioned: are you saying that this >> description is written too verbosely? >> Then, do you think there are still issues with the revised version? >> interrupts: >> minItems: 1 >> maxItems: 8 >> description: >> Either one interrupt per channel (8 interrupts), or one >> combined interrupt for all channels. > > No, it is not wrapped according to Linux coding style. > > Please wrap code according to the preferred limit expressed in Kernel > coding style (checkpatch is not a coding style description, but only a > tool). However don't wrap blindly (see Kernel coding style). > Thank you for your patience. I have clearly understood your points and will incorporate all of your feedback when revising the V3 version of the patch. Best regards, Jun
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. Peter > > > > Signed-off-by: Jun Guo <jun.guo@cixtech.com> > > Link: https://lore.kernel.org/r/20251216123026.3519923-2-jun.guo@cixtech.com > > What does this express? Changelog link? Then keep it in the changelog > --- part. > > > > --- > > .../devicetree/bindings/dma/arm,dma-350.yaml | 31 +++++++++++++------ > > 1 file changed, 21 insertions(+), 10 deletions(-) > > > > diff --git a/Documentation/devicetree/bindings/dma/arm,dma-350.yaml b/Documentation/devicetree/bindings/dma/arm,dma-350.yaml > > index 429f682f15d8..3639ce0d5054 100644 > > --- a/Documentation/devicetree/bindings/dma/arm,dma-350.yaml > > +++ b/Documentation/devicetree/bindings/dma/arm,dma-350.yaml > > @@ -14,7 +14,11 @@ allOf: > > > > properties: > > compatible: > > - const: arm,dma-350 > > + oneOf: > > + - const: arm,dma-350 > > + - items: > > + - const: cix,sky1-dma-350 > > + - const: arm,dma-350 > > > > reg: > > items: > > @@ -22,15 +26,22 @@ properties: > > > > interrupts: > > minItems: 1 > > - items: > > - - description: Channel 0 interrupt > > - - description: Channel 1 interrupt > > - - description: Channel 2 interrupt > > - - description: Channel 3 interrupt > > - - description: Channel 4 interrupt > > - - description: Channel 5 interrupt > > - - description: Channel 6 interrupt > > - - description: Channel 7 interrupt > > + maxItems: 8 > > + description: | > > + The DMA controller may be configured with separate interrupts for each channel, > > + or with a single combined interrupt for all channels, depending on the SoC integration. > > And more important - you must review the LLM microslop output before > posting and adjust it to Linux kernel coding style. Don't send > unredacted tool output. > > Best regards, > Krzysztof > -- Best regards, Peter
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 ignored rest of the email message, so I assume you agree that you should not send LLM microslop? Best regards, Krzysztof
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? WARNING: Non-standard signature: Assisted-by: #14: Assisted-by: Cursor: GPT-5.3 Codex ERROR: Unrecognized email address: 'Cursor: GPT-5.3 Codex' #14: Assisted-by: Cursor: GPT-5.3 Codex > You ignored rest of the email > message, so I assume you agree that you should not send LLM microslop? > I am not the patch author, Jun will reply it. I come in to discuss this patch duo to I suggested Jun adding LLM tag at patch context. -- Best regards, Peter
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... > > WARNING: Non-standard signature: Assisted-by: > #14: > Assisted-by: Cursor: GPT-5.3 Codex > > ERROR: Unrecognized email address: 'Cursor: GPT-5.3 Codex' > #14: > Assisted-by: Cursor: GPT-5.3 Codex > >> You ignored rest of the email >> message, so I assume you agree that you should not send LLM microslop? >> > > I am not the patch author, Jun will reply it. Ah, sorry, I did not notice that. Best regards, Krzysztof
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? > >> >> WARNING: Non-standard signature: Assisted-by: >> #14: >> Assisted-by: Cursor: GPT-5.3 Codex >> >> ERROR: Unrecognized email address: 'Cursor: GPT-5.3 Codex' >> #14: >> Assisted-by: Cursor: GPT-5.3 Codex >> >>> You ignored rest of the email >>> message, so I assume you agree that you should not send LLM microslop? >>> >> >> I am not the patch author, Jun will reply it. > > Ah, sorry, I did not notice that. > > > Best regards, > Krzysztof Best regards, Jun
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
On 3/23/2026 3:27 PM, Krzysztof Kozlowski wrote: > EXTERNAL EMAIL > > 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? Sorry, I overlooked the programming assistant guidelines. I will comply with the requirements of the programming assistant guidelines and resubmit a new patch. > > Best regards, > Krzysztof Best regards, Jun
© 2016 - 2026 Red Hat, Inc.