From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Stone Red <redstone.dcity@gmail.com>
Cc: andersson@kernel.org, konradybcio@kernel.org,
conor+dt@kernel.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, ShiTou Hong <dc_redstone@outlook.com>,
KancyJoe <kancy2333@outlook.com>
Subject: Re: [PATCH v2 2/6] arm64: dts: qcom: sm8250-hdk: Add LT9611UXC HDMI bridge
Date: Tue, 27 Oct 2026 11:52:13 +0100 [thread overview]
Message-ID: <b971335b-e7ff-48a0-a1c7-9f369a3ca75c@oss.qualcomm.com> (raw)
In-Reply-To: <CALkEBsyQCJwoDiR_dnqfVynEUGBi-qNenE+1oAFADPC-6OOBZQ@mail.gmail.com>
On 10/27/26 9:56 AM, Stone Red wrote:
> Btw, there are some misplaced `status` properties in the original dts file,
> am I supposed to fix them together?
I think it's good to keep the new style for new nodes. If you wish to
do it manually (or maybe ask an LLM), updating the file itself would
be a good improvement too
Konrad
next prev parent reply other threads:[~2026-10-27 10:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 8:07 [PATCH v2 0/6] arm64: dts: qcom: sm8250-hdk: Enable additional peripherals ShiTou Hong
2026-10-27 8:07 ` [PATCH v2 1/6] arm64: dts: qcom: sm8250-hdk: Enable the sdhc_2 port ShiTou Hong
2026-10-27 8:31 ` Konrad Dybcio
2026-10-27 8:07 ` [PATCH v2 2/6] arm64: dts: qcom: sm8250-hdk: Add LT9611UXC HDMI bridge ShiTou Hong
2026-10-27 8:34 ` Konrad Dybcio
[not found] ` <CALkEBsyQCJwoDiR_dnqfVynEUGBi-qNenE+1oAFADPC-6OOBZQ@mail.gmail.com>
2026-10-27 10:52 ` Konrad Dybcio [this message]
2026-10-27 11:33 ` Stone Red
2026-10-27 8:07 ` [PATCH v2 3/6] arm64: dts: qcom: sm8250-hdk: Add FSA4480 USB-C protocol chip ShiTou Hong
2026-10-27 8:07 ` [PATCH v2 4/6] arm64: dts: qcom: sm8250-hdk: Enable the PCIe ports ShiTou Hong
2026-10-27 8:33 ` Konrad Dybcio
2026-10-27 8:07 ` [PATCH v2 5/6] arm64: dts: qcom: sm8250-hdk: Add support of QCA6390 ShiTou Hong
2026-10-27 8:07 ` [PATCH v2 6/6] arm64: dts: qcom: sm8250-hdk: Add PM8150b LEDs ShiTou Hong
2026-10-27 8:33 ` Konrad Dybcio
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=b971335b-e7ff-48a0-a1c7-9f369a3ca75c@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=dc_redstone@outlook.com \
--cc=devicetree@vger.kernel.org \
--cc=kancy2333@outlook.com \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=redstone.dcity@gmail.com \
/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