mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Zeynep Dicle <zeynep.dicle.dev@gmail.com>,
	robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org
Cc: bartosz.golaszewski@oss.qualcomm.com, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, daniel.baluta@nxp.com,
	simona.toaca@nxp.com, d-gole@ti.com, m-chawdhry@ti.com
Subject: Re: [PATCH] dt-bindings: bus: ti,da850-mstpri: Convert to YAML
Date: Fri, 13 Mar 2026 19:40:02 +0100	[thread overview]
Message-ID: <346aba2a-2d7c-4b19-b0d7-f7a04a53b99f@kernel.org> (raw)
In-Reply-To: <44931dca-171e-4fae-ac37-761e5eb95d3a@kernel.org>

On 13/03/2026 18:41, Krzysztof Kozlowski wrote:
> On 13/03/2026 18:31, Zeynep Dicle wrote:
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/bus/ti,da850-mstpri.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +title: Texas Instruments DA850 Master Peripheral Priority
>> +maintainers:
>> +  - Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
>> +description: |
>> +  DA8XX SoCs feature a set of registers allowing to change the priority of all
>> +  peripherals classified as masters.
>> +properties:
>> +  compatible:
>> +    const: ti,da850-mstpri
>> +  reg:
>> +    maxItems: 1
>> +required:
>> +  - compatible
>> +  - reg
> 
> I don't believe this passed your GSoC mentors review. Please don't send
> AI output but actually follow existing kernel/DT style.

And let me remind, that what you sent is not better what Rob already
prepared a year ago:

https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git/commit/?h=dt-convert&id=9f0479e32bcd132e85899b40185c62754ff93aed

So what is the point of posting unsupervised and poor AI output if we
have it all done?

Best regards,
Krzysztof

      reply	other threads:[~2026-03-13 18:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-13 17:31 Zeynep Dicle
2026-03-13 17:41 ` Krzysztof Kozlowski
2026-03-13 18:40   ` Krzysztof Kozlowski [this message]

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=346aba2a-2d7c-4b19-b0d7-f7a04a53b99f@kernel.org \
    --to=krzk@kernel.org \
    --cc=bartosz.golaszewski@oss.qualcomm.com \
    --cc=conor+dt@kernel.org \
    --cc=d-gole@ti.com \
    --cc=daniel.baluta@nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m-chawdhry@ti.com \
    --cc=robh@kernel.org \
    --cc=simona.toaca@nxp.com \
    --cc=zeynep.dicle.dev@gmail.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

Powered by JetHome