From: Krzysztof Kozlowski <krzk@kernel.org>
To: Rudraksha Gupta <guptarud@gmail.com>,
David Heidelberg <david@ixit.cz>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/4] ARM: dts: qcom: msm8960: expressatt: Sort node references and includes
Date: Sat, 11 Apr 2026 09:38:16 +0200 [thread overview]
Message-ID: <f51ddaf0-a857-4250-ad9e-e50982e8c108@kernel.org> (raw)
In-Reply-To: <a0eb87b5-7bb8-4aae-83a1-982d8b4c06f8@gmail.com>
On 11/04/2026 06:01, Rudraksha Gupta wrote:
> On 4/7/26 14:46, David Heidelberg wrote:
>> On 07/04/2026 23:04, Krzysztof Kozlowski wrote:
>>> On 07/04/2026 22:39, Rudraksha Gupta wrote:
>>>> On 4/7/26 12:59, Krzysztof Kozlowski wrote:
>>>>> On 01/04/2026 22:32, Rudraksha Gupta via B4 Relay wrote:
>>>>>> From: Rudraksha Gupta <guptarud@gmail.com>
>>>>>>
>>>>>> Reorganize the DTS file for consistency with other msm8960 board
>>>>>> files.
>>>>>>
>>>>>> Assisted-by: Claude:claude-opus-4.6
>>>>>> Signed-off-by: Rudraksha Gupta <guptarud@gmail.com>
>>>>>> ---
>>>>>> .../dts/qcom/qcom-msm8960-samsung-expressatt.dts | 408
>>>>>> +++++++++++----------
>>>>>> 1 file changed, 207 insertions(+), 201 deletions(-)
>>>>>>
>>>>> Sorry, but no. We are not taking Claude as one determining coding
>>>>> style.
>>>>> Are we going to do the work again the moment we come with proper tool?
>>>>
>>>> There is no tool currently to auto format DTS, and doesn't seem to be
>>>> coming for a while:
>>>>
>>>> https://www.youtube.com/watch?v=cvoIbTL_ZQA
>>>>
>>>>
>>>> Claude didn't determine the coding style. I did based on sony-huashan,
>>>> which is already upstream:
>>>>
>>>> https://github.com/torvalds/linux/blob/master/arch/arm/boot/dts/qcom/qcom-msm8960-sony-huashan.dts
>>>>
>>>>
>>>>
>>>> I just used Claude to do the manual work for me. In v2, I made sure the
>>>> diff before and after the change was nill. v3 included additional
>>>> changes requested by Konrad and some comments that I remembered during
>>>> prior attempts mainlining patch series for this device.
>>>
>>> IMO, it is just too risky to let Claude reorganize the nodes, but I
>>> assume reviewers of your code did run dtx_diff.
>>
>> I think it depends on the prompt. Since I’m performing many of the
>> same tasks repeatedly across multiple sdm845 devices, asking an LLM to
>> do node-by-node reorganization can be reasonably reviewable (at least
>> when reviewing incremental progress, not just the final diff).
>>
>> I would prefer to do more of the sorting myself, but I find it quite
>> tedious. The diff tool struggles when similar or identical lines
>> appear in different nodes, which often results in a messy final diff
>> (I noticed this in Sajattack’s sdm845 LG patchset).
>>
>> This leads me to an idea:
>>
>> For these sorting cleanups, perhaps we could introduce a “squash mode”?
>>
>> Contributors could submit commits per node, making the reorganization
>> clearly visible (and ensuring nothing is accidentally lost), and then
>> the maintainer could squash them into a single commit to avoid
>> cluttering the git log.
>>
>> What do you think?
>
> Easiest solution would be to get Claude to make a DTS auto formatter. I
> estimate it would likely take a couple iterations to get a functional
> prototype and max a week to get it into a mergable state, if the style
> is agreed beforehand. Simply provide DTS'es that follow the pattern you
> like to Claude, then tell Claude that you want to make a Python script
Yeah, and who wants to review the Claude code?
I already have a formatter to review in the pipeline...
> to auto format DTS files and make functions for each different common
> style pattern identified in the DTS'es. I assume it would give a good
> enough base to work off of. The most painful part will be determining
> what the correct style for all DTS'es as I'm sure others will have
> opinions on that.
>
The biggest problem is that no way maintainers will run untrusted 3rd
party code, co-contributed by random people with Claude.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-04-11 7:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-01 20:32 [PATCH v3 0/4] Reorganize DTS and add fuel-gauge to samsung-expressatt Rudraksha Gupta via B4 Relay
2026-04-01 20:32 ` [PATCH v3 1/4] ARM: dts: qcom: msm8960: expressatt: Sort node references and includes Rudraksha Gupta via B4 Relay
2026-04-02 8:53 ` Konrad Dybcio
2026-04-07 19:59 ` Krzysztof Kozlowski
2026-04-07 20:39 ` Rudraksha Gupta
2026-04-07 21:04 ` Krzysztof Kozlowski
2026-04-07 21:29 ` Rudraksha Gupta
2026-04-07 21:46 ` David Heidelberg
2026-04-11 4:01 ` Rudraksha Gupta
2026-04-11 7:38 ` Krzysztof Kozlowski [this message]
2026-04-11 8:33 ` David Heidelberg
2026-04-11 7:36 ` Krzysztof Kozlowski
2026-04-01 20:32 ` [PATCH v3 2/4] ARM: dts: qcom: msm8960: Flatten I2C pinctrl state subnodes Rudraksha Gupta via B4 Relay
2026-04-02 8:53 ` Konrad Dybcio
2026-04-01 20:32 ` [PATCH v3 3/4] ARM: dts: qcom: msm8960: Add GSBI5 I2C controller Rudraksha Gupta via B4 Relay
2026-04-11 15:20 ` Dmitry Baryshkov
2026-04-01 20:32 ` [PATCH v3 4/4] ARM: dts: qcom: msm8960: expressatt: Add MAX17048 fuel gauge Rudraksha Gupta via B4 Relay
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=f51ddaf0-a857-4250-ad9e-e50982e8c108@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=david@ixit.cz \
--cc=devicetree@vger.kernel.org \
--cc=guptarud@gmail.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox