From: Umang Chheda <umang.chheda@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: andersson@kernel.org, konradybcio@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
richardcochran@gmail.com, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/4] arm64: dts: qcom: monaco-evk: Extract common EVK hardware into shared dtsi
Date: Wed, 10 Jun 2026 12:27:51 +0530 [thread overview]
Message-ID: <751d1fd2-4f34-40bb-9175-bff749feef6c@oss.qualcomm.com> (raw)
In-Reply-To: <vnax3dacoobn3hsx3xf7dnfloxv7qbjxqjwkwnxc3ux6jbqo2w@3zroc5uxgfg5>
Hi Dmitry,
On 5/13/2026 8:03 PM, Dmitry Baryshkov wrote:
> Judged on the previous suggestions by DT maintainers, there should be
> separate DTS files.
Ack, I will post the next version of series with seperate DT for this
board similar to v2.
Thanks,
Umang
next prev parent reply other threads:[~2026-06-10 6:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 17:05 [PATCH v4 0/4] arm64: dts: qcom: Introduce support for monaco-ac-evk Umang Chheda
2026-04-27 17:05 ` [PATCH v4 1/4] arm64: dts: qcom: monaco-evk: Extract common EVK hardware into shared dtsi Umang Chheda
2026-05-04 12:57 ` Konrad Dybcio
2026-05-04 18:28 ` Umang Chheda
2026-05-04 20:19 ` Krzysztof Kozlowski
2026-05-05 13:53 ` Umang Chheda
2026-05-06 9:18 ` Konrad Dybcio
2026-05-12 8:12 ` Umang Chheda
2026-05-04 18:44 ` Dmitry Baryshkov
2026-05-04 19:26 ` Umang Chheda
2026-05-04 23:28 ` Dmitry Baryshkov
2026-05-05 13:47 ` Umang Chheda
2026-05-13 14:33 ` Dmitry Baryshkov
2026-06-10 6:57 ` Umang Chheda [this message]
2026-04-27 17:05 ` [PATCH v4 2/4] dt-bindings: arm: qcom: Add monaco-ac-evk support Umang Chheda
2026-04-27 17:05 ` [PATCH v4 3/4] arm64: dts: qcom: monaco: Add monaco-ac EVK board Umang Chheda
2026-05-04 12:53 ` Konrad Dybcio
2026-05-04 19:16 ` Umang Chheda
2026-05-06 9:17 ` Konrad Dybcio
2026-04-27 17:05 ` [PATCH v4 4/4] arm64: dts: qcom: monaco-ac-evk: Add IFP mezzanine Umang Chheda
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=751d1fd2-4f34-40bb-9175-bff749feef6c@oss.qualcomm.com \
--to=umang.chheda@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=robh@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®