From: Krzysztof Kozlowski <krzk@kernel.org>
To: Kaustabh Chakraborty <kauschluss@disroot.org>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/7] arm64: dts: exynos7870: relocate ${x}-names property after ${x}
Date: Tue, 7 Oct 2025 10:22:41 +0900 [thread overview]
Message-ID: <8a3b5248-ff46-4aaf-9797-202f85ef9b23@kernel.org> (raw)
In-Reply-To: <6dff1e8256f3d0932d1f5ad941e129db@disroot.org>
On 29/09/2025 19:01, Kaustabh Chakraborty wrote:
> On 2025-09-28 21:56, Krzysztof Kozlowski wrote:
>> On Mon, 29 Sept 2025 at 01:44, Kaustabh Chakraborty
>> <kauschluss@disroot.org> wrote:
>>>
>>> All ${x}-names properties are conventionally placed after their
>>> corresponding ${x} properties. For instance, 'clock-names' must follow
>>> 'clocks', 'interrupt-names' must follow 'interrupts'. Make necessary
>>> changes to follow said convention. No functional changes made.
>>>
>>
>> I don't intend to take such cosmetic changes, because they interfere
>> with stable back porting, unless we have a tool for such cleanup. Did
>> you use my prototype tool for that or some other tool?
>
> No, I did it manually. This is due to your first remark in [1] and
> my corresponding reply in [2]. What do I do here then?
I asked for the new code to follow this style, but I don't want to fix
yet existing code - before we come with a tool doing it.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-10-07 1:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-28 16:43 [PATCH 0/7] Another set of exynos7870 devicetree fixes Kaustabh Chakraborty
2025-09-28 16:43 ` [PATCH 1/7] arm64: dts: exynos7870: relocate ${x}-names property after ${x} Kaustabh Chakraborty
2025-09-28 21:56 ` Krzysztof Kozlowski
2025-09-29 10:01 ` Kaustabh Chakraborty
2025-10-07 1:22 ` Krzysztof Kozlowski [this message]
2025-10-13 8:24 ` Kaustabh Chakraborty
2025-09-28 16:43 ` [PATCH 2/7] arm64: dts: exynos7870-a2corelte: " Kaustabh Chakraborty
2025-09-28 16:43 ` [PATCH 3/7] arm64: dts: exynos7870-j6lte: " Kaustabh Chakraborty
2025-09-28 16:43 ` [PATCH 4/7] arm64: dts: exynos7870-on7xelte: " Kaustabh Chakraborty
2025-09-28 16:43 ` [PATCH 5/7] arm64: dts: exynos7870-a2corelte: add bus-width to mmc0 node Kaustabh Chakraborty
2025-10-13 0:25 ` (subset) " Krzysztof Kozlowski
2025-09-28 16:43 ` [PATCH 6/7] arm64: dts: exynos7870-j6lte: " Kaustabh Chakraborty
2025-10-13 0:25 ` (subset) " Krzysztof Kozlowski
2025-09-28 16:43 ` [PATCH 7/7] arm64: dts: exynos7870-on7xelte: " Kaustabh Chakraborty
2025-10-13 0:26 ` (subset) " Krzysztof Kozlowski
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=8a3b5248-ff46-4aaf-9797-202f85ef9b23@kernel.org \
--to=krzk@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kauschluss@disroot.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@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;
as well as URLs for NNTP newsgroup(s).