From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Kathiravan T <quic_kathirav@quicinc.com>,
agross@kernel.org, andersson@kernel.org,
konrad.dybcio@linaro.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 2/2] arm64: dts: qcom: ipq5332: add support for the RDP468 variant
Date: Thu, 23 Mar 2023 11:56:47 +0100 [thread overview]
Message-ID: <3b2e7b07-7598-45af-0dce-a60310aa5d60@linaro.org> (raw)
In-Reply-To: <20230323093120.20558-3-quic_kathirav@quicinc.com>
On 23/03/2023 10:31, Kathiravan T wrote:
> Add the initial device tree support for the Reference Design
> Platform(RDP) 468 based on IPQ5332 family of SoCs. This patch carries the
> support for Console UART, SPI NOR, eMMC.
>
> Signed-off-by: Kathiravan T <quic_kathirav@quicinc.com>
> ---
> Changes in V2:
> - Moved the 'reg' property after 'compatible'
>
> arch/arm64/boot/dts/qcom/Makefile | 1 +
> arch/arm64/boot/dts/qcom/ipq5332-rdp468.dts | 103 ++++++++++++++++++++
> 2 files changed, 104 insertions(+)
> create mode 100644 arch/arm64/boot/dts/qcom/ipq5332-rdp468.dts
Hi,
Your v1 was reported that it does not build. Does this patch build fine?
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-03-23 10:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 9:31 [PATCH V2 0/2] Add initial support for RDP468 of IPQ5332 family Kathiravan T
2023-03-23 9:31 ` [PATCH V2 1/2] dt-bindings: arm: qcom: document MI01.6 board based on " Kathiravan T
2023-03-23 9:32 ` Krzysztof Kozlowski
2023-03-23 9:31 ` [PATCH V2 2/2] arm64: dts: qcom: ipq5332: add support for the RDP468 variant Kathiravan T
2023-03-23 10:56 ` Krzysztof Kozlowski [this message]
2023-03-23 11:17 ` Kathiravan T
2023-03-23 12:42 ` Kathiravan T
2023-04-06 11:22 ` [PATCH V2 0/2] Add initial support for RDP468 of IPQ5332 family Kathiravan T
2023-04-07 23:40 ` (subset) " Bjorn Andersson
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=3b2e7b07-7598-45af-0dce-a60310aa5d60@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_kathirav@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
all inboxes | Powered by JetHome®