From: Krzysztof Kozlowski <krzk@kernel.org>
To: Dragan Simic <dsimic@manjaro.org>
Cc: linux-rockchip@lists.infradead.org, heiko@sntech.de,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
linux-kernel@vger.kernel.org,
Diederik de Haas <didi.debian@cknow.org>
Subject: Re: [PATCH] arm64: dts: rockchip: Add a few aliases to the PineTab2 dtsi
Date: Thu, 5 Sep 2024 13:48:10 +0200 [thread overview]
Message-ID: <6b51f810-438c-42fe-92c2-87966906b534@kernel.org> (raw)
In-Reply-To: <946b8248f5b282a8532c8532a3eda98e@manjaro.org>
On 05/09/2024 13:43, Dragan Simic wrote:
> Hello Krzysztof,
>
> On 2024-09-05 13:39, Krzysztof Kozlowski wrote:
>> On 05/09/2024 13:32, Dragan Simic wrote:
>>> Sprinkle a few commonly used aliases onto the PineTab2 dtsi file, to
>>> improve
>>> its readability a bit, to make it easier to refer to the actual nodes
>>> later,
>>> if needed, and to add a bit more detail to some of the labels.
>>>
>>> No functional changes are introduced, which was validated by
>>> decompiling and
>>> comparing all affected board dtb files before and after these changes.
>>> When
>>> compared with the decompiled original dtb files, some of the phandles
>>> in the
>>> updated dtb files have different values, and the updated dtb files
>>> contain
>>> some additional phandles and additional symbols that come from the
>>> introduced
>>> aliases, but they still effectively remain the same as the originals.
>>>
>>> Suggested-by: Diederik de Haas <didi.debian@cknow.org>
>>> Signed-off-by: Dragan Simic <dsimic@manjaro.org>
>>> ---
>>
>> Unused aliases do not improve readability, so for me this change is
>> making code worse without valid reason.
>
> Then why do we already have, for example, unused "rk817_charger:
> charger"
> aliases in quite a few board dts(i) files? If those are actually seen
Ask contributors...
> as
> redundant, we should remove all of them.
They are already there, so dropping them is close to unnecessary churn.
And quite a lot of work to investigate the reason behind EACH label.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-09-05 11:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 11:32 [PATCH] arm64: dts: rockchip: Add a few aliases to the PineTab2 dtsi Dragan Simic
2024-09-05 11:39 ` Krzysztof Kozlowski
2024-09-05 11:43 ` Dragan Simic
2024-09-05 11:48 ` Krzysztof Kozlowski [this message]
2024-09-05 11:55 ` Dragan Simic
2024-09-05 12:21 ` Diederik de Haas
2024-09-05 14:08 ` Heiko Stübner
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=6b51f810-438c-42fe-92c2-87966906b534@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=didi.debian@cknow.org \
--cc=dsimic@manjaro.org \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.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