From: Bjorn Andersson <andersson@kernel.org>
To: luca@z3ntu.xyz, linux-arm-msm@vger.kernel.org
Cc: phone-devel@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
agross@kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
~postmarketos/upstreaming@lists.sr.ht,
Konrad Dybcio <konrad.dybcio@somainline.org>
Subject: Re: (subset) [PATCH 1/3] ARM: dts: qcom: ipq8064-rb3011: fix nand node validation
Date: Mon, 17 Oct 2022 22:05:49 -0500 [thread overview]
Message-ID: <166606235861.3553294.8715702430694617342.b4-ty@kernel.org> (raw)
In-Reply-To: <20221013190657.48499-1-luca@z3ntu.xyz>
On Thu, 13 Oct 2022 21:06:55 +0200, Luca Weiss wrote:
> The devicetree documentation for the nand node requires the subnode be
> called nand@ and no compatible is needed.
>
>
Applied, thanks!
[1/3] ARM: dts: qcom: ipq8064-rb3011: fix nand node validation
commit: 6f917ec31d3eb0f2c657f36d299d39bd8d051e03
[2/3] ARM: dts: qcom: apq8084: fix compatible for l2-cache
commit: 891bcfe02470c79489987d643ba0010c0b16f896
[3/3] ARM: dts: qcom: apq8064: fix coresight compatible
commit: a42b1ee868361f1cb0492f1bdaefb43e0751e468
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2022-10-18 3:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 19:06 [PATCH 1/3] ARM: dts: qcom: ipq8064-rb3011: fix nand node validation Luca Weiss
2022-10-13 19:06 ` [PATCH 2/3] ARM: dts: qcom: apq8084: fix compatible for l2-cache Luca Weiss
2022-10-13 19:46 ` Konrad Dybcio
2022-10-13 21:16 ` Krzysztof Kozlowski
2022-10-13 19:06 ` [PATCH 3/3] ARM: dts: qcom: apq8064: fix coresight compatible Luca Weiss
2022-10-13 19:47 ` Konrad Dybcio
2022-10-13 21:17 ` Krzysztof Kozlowski
2022-10-13 19:46 ` [PATCH 1/3] ARM: dts: qcom: ipq8064-rb3011: fix nand node validation Konrad Dybcio
2022-10-13 21:16 ` Krzysztof Kozlowski
2022-10-18 3:05 ` 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=166606235861.3553294.8715702430694617342.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=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca@z3ntu.xyz \
--cc=phone-devel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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).