From: Bjorn Andersson <andersson@kernel.org>
To: linux-arm-msm@vger.kernel.org,
Bjorn Andersson <andersson@kernel.org>,
robh+dt@kernel.org, linux-kernel@vger.kernel.org,
konrad.dybcio@somainline.org, devicetree@vger.kernel.org,
krzysztof.kozlowski+dt@linaro.org, agross@kernel.org,
krzysztof.kozlowski@linaro.org
Subject: Re: (subset) [PATCH 1/4] ARM: dts: qcom: msm8960: override nodes by label
Date: Mon, 29 Aug 2022 18:45:55 -0500 [thread overview]
Message-ID: <166181675978.322065.8113362437480273235.b4-ty@kernel.org> (raw)
In-Reply-To: <20220810080516.166866-1-krzysztof.kozlowski@linaro.org>
On Wed, 10 Aug 2022 11:05:13 +0300, Krzysztof Kozlowski wrote:
> Using node paths to extend or override a device tree node is error
> prone. If there was a typo error, a new node will be created instead of
> extending the existing node. This will lead to run-time errors that
> could be hard to detect.
>
> A mistyped label on the other hand, will cause a dtc compile error
> (during build time). This also reduces the indentation making the code
> easier to read.
>
> [...]
Applied, thanks!
[1/4] ARM: dts: qcom: msm8960: override nodes by label
commit: cb9d7639491466d7296d30ec43045391c3a34651
[2/4] ARM: dts: qcom: msm8226: override nodes by label
commit: c77ad7f3ba7ffa05f49516732886f5feed95793b
[3/4] ARM: dts: qcom: msm8660: override nodes by label
commit: 5bd858a82ab77333b41bda9049fbaf6f878c11ab
[4/4] ARM: dts: qcom: msm8660-surf: move fixed regulator out of soc
commit: 7c7a05390b5e4f44787b6703e5a3b836c3327b0f
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2022-08-29 23:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-10 8:05 Krzysztof Kozlowski
2022-08-10 8:05 ` [PATCH 2/4] ARM: dts: qcom: msm8226: " Krzysztof Kozlowski
2022-08-10 8:05 ` [PATCH 3/4] ARM: dts: qcom: msm8660: " Krzysztof Kozlowski
2022-08-10 8:05 ` [PATCH 4/4] ARM: dts: qcom: msm8660-surf: move fixed regulator out of soc Krzysztof Kozlowski
2022-08-29 23:45 ` Bjorn Andersson [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=166181675978.322065.8113362437480273235.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=agross@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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
all inboxes | Powered by JetHome®