From: Yongxing Mou <quic_yongmou@quicinc.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: <linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: dts: qcom: hamoa-iot-evk: Enable display support
Date: Wed, 23 Jul 2025 17:24:18 +0800 [thread overview]
Message-ID: <7baebfcf-3afd-445c-ab88-a8ca503c2e33@quicinc.com> (raw)
In-Reply-To: <f5f30f4e-50ee-4539-893b-4a7667a16651@kernel.org>
On 2025/7/23 17:08, Krzysztof Kozlowski wrote:
> WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.
>
> On 23/07/2025 10:08, Yongxing Mou wrote:
>>>> ---
>>>> This change made top of initial DTS:
>>>> https://lore.kernel.org/all/20250716-hamoa_initial-v1-0-f6f5d0f9a163@oss.qualcomm.com/
>>>> ---
>>>> arch/arm64/boot/dts/qcom/hamoa-iot-evk.dts | 156 +++++++++++++++++++++++++++++
>>>> 1 file changed, 156 insertions(+)
>>>
>>> Just squash it there. Why are you posting knowingly incomplete DTS just
>>> to fix it later?
>>>
>>> Best regards,
>>> Krzysztof
>> Hi, sorry, I'm just want to enable display based initial DTS. Should
>> this patch merge into the initial DTS?
>
>
> Yes, initial DTS is not merged and being reviewed. Adding new board is
> one commit, not two.
>
>
> Best regards,
> Krzysztof
Got it. Thanks~ will merge into one patch.
next prev parent reply other threads:[~2025-07-23 9:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 6:14 Yongxing Mou
2025-07-23 6:26 ` Krzysztof Kozlowski
2025-07-23 8:08 ` Yongxing Mou
2025-07-23 9:08 ` Krzysztof Kozlowski
2025-07-23 9:24 ` Yongxing Mou [this message]
2025-07-23 11:21 ` Dmitry Baryshkov
2025-07-24 7:40 ` Yongxing Mou
2025-07-25 11:15 ` Dmitry Baryshkov
2025-07-23 11:38 ` Konrad Dybcio
2025-07-24 6:13 ` Yongxing Mou
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=7baebfcf-3afd-445c-ab88-a8ca503c2e33@quicinc.com \
--to=quic_yongmou@quicinc.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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®