From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Parikshit Pareek <quic_ppareek@quicinc.com>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Andrew Halaney <ahalaney@redhat.com>
Subject: Re: [PATCH v3 2/3] arm64: dts: qcom: sa8295p: move common nodes to dtsi
Date: Tue, 16 Aug 2022 13:06:44 +0300 [thread overview]
Message-ID: <7532753c-60d6-a8cd-b462-bcbf01035d89@linaro.org> (raw)
In-Reply-To: <20220812165453.11608-3-quic_ppareek@quicinc.com>
On 12/08/2022 19:54, Parikshit Pareek wrote:
> There are many ADP boards with lot of common features. Move common
> nodes to sa8540p-adp.dtsi file. This will be base for many ADP boards
> to be introduced in near future.
>
> Signed-off-by: Parikshit Pareek <quic_ppareek@quicinc.com>
> ---
> arch/arm64/boot/dts/qcom/sa8295p-adp.dts | 377 +--------------------
> arch/arm64/boot/dts/qcom/sa8540p-adp.dtsi | 384 ++++++++++++++++++++++
Please send patch with tweaking -B/-M/-C parameters, so the copy is
properly detected.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-08-16 10:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 16:54 [PATCH v3 0/3] arm64: dts: qcom: add dts for sa8540p-ride board Parikshit Pareek
2022-08-12 16:54 ` [PATCH v3 1/3] dt-bindings: arm: qcom: Document additional sa8540p device Parikshit Pareek
2022-08-12 16:54 ` [PATCH v3 2/3] arm64: dts: qcom: sa8295p: move common nodes to dtsi Parikshit Pareek
2022-08-15 15:00 ` Brian Masney
2022-08-16 10:06 ` Krzysztof Kozlowski [this message]
2022-08-12 16:54 ` [PATCH v3 3/3] arm64: dts: qcom: introduce sa8540p-ride dts Parikshit Pareek
2022-08-23 20:10 ` Andrew Halaney
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=7532753c-60d6-a8cd-b462-bcbf01035d89@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=ahalaney@redhat.com \
--cc=bjorn.andersson@linaro.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=quic_ppareek@quicinc.com \
--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;
as well as URLs for NNTP newsgroup(s).