From: Svyatoslav Ryhel <clamor95@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Jonathan Hunter <jonathanh@nvidia.com>,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/1] ARM: tegra: transformer: use labels for mmc in aliases
Date: Wed, 16 Aug 2023 19:40:52 +0300 [thread overview]
Message-ID: <900CEBDC-61FB-4123-9E1F-18D18FF0B2CD@gmail.com> (raw)
In-Reply-To: <ZNz6VyWASDV2Srie@orome>
16 серпня 2023 р. 19:33:27 GMT+03:00, Thierry Reding <thierry.reding@gmail.com> написав(-ла):
>On Sun, Jul 30, 2023 at 03:51:50PM +0300, Svyatoslav Ryhel wrote:
>> Use phandle references for mmc instead of path in aliases.
>>
>> Signed-off-by: Svyatoslav Ryhel <clamor95@gmail.com>
>> ---
>> arch/arm/boot/dts/tegra114-asus-tf701t.dts | 12 ++++++------
>> .../boot/dts/tegra30-asus-transformer-common.dtsi | 12 ++++++------
>> 2 files changed, 12 insertions(+), 12 deletions(-)
>
>The commit message doesn't describe why this is useful and without any
>clarification I don't see any benefit in doing this.
1. Simplify comprehension of aliases, path is harder to read then a label
2. Unify with other t20 and t30 trees (paz00, tf101, grouper, picasso etc)
>Thierry
prev parent reply other threads:[~2023-08-16 16:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-30 12:51 [PATCH v1 0/1] Transformers: switch from paths to labels in device tree Svyatoslav Ryhel
2023-07-30 12:51 ` [PATCH v1 1/1] ARM: tegra: transformer: use labels for mmc in aliases Svyatoslav Ryhel
2023-08-16 16:33 ` Thierry Reding
2023-08-16 16:40 ` Svyatoslav Ryhel [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=900CEBDC-61FB-4123-9E1F-18D18FF0B2CD@gmail.com \
--to=clamor95@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@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
all inboxes | Powered by JetHome®