From: Daniel Carter <yass27106@gmail.com>
To: krzk@kernel.org, andersson@kernel.org, konradybcio@kernel.org
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
yass27106@gmail.com
Subject: Re: [PATCH v5 2/3] arm64: dts: qcom: add device tree for Asus Vivobook 16 X1607QA
Date: Sun, 22 Nov 2026 02:14:45 -0800 (PST) [thread overview]
Message-ID: <2920a713778046808ee4a8c2b12002f2@gmail.com> (raw)
In-Reply-To: <sashiko-outbox-217692@kernel.org>
Hi Krzysztof, hi all,
A friendly ping on this one - no rush, just making sure it did not fall
through the cracks.
Patches 1/3 and 3/3 already carry Krzysztof's Acked-by and Srini's
Reviewed-by; only 2/3 (the device tree itself) is still awaiting review.
On the panel question Sashiko raised: the panel node is inherited from the
shared x1-asus-vivobook-s15.dtsi, and display output works correctly on
this hardware with it (iGPU-accelerated desktop). The exact panel model has
not been identified from EDID yet - I can send a follow-up refining the
panel description once it is, or adjust it in this series beforehand if you
would prefer that before the board is merged.
Is there anything else you would like changed in 2/3?
Best regards,
Daniel Carter
prev parent reply other threads:[~2026-11-22 10:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 20:55 [PATCH v5 0/3] arm64: dts: qcom: add device tree for Asus Vivobook 16 X1607QA Daniel Carter
2026-11-16 20:55 ` [PATCH v5 1/3] dt-bindings: arm: qcom: document " Daniel Carter
2026-11-16 20:55 ` [PATCH v5 2/3] arm64: dts: qcom: add device tree for " Daniel Carter
2026-11-16 20:55 ` [PATCH v5 3/3] soundwire: qcom: check clk_prepare_enable() return values Daniel Carter
2026-11-22 15:41 ` Daniel Carter
[not found] ` <sashiko-outbox-217692@kernel.org>
2026-11-22 10:14 ` Daniel Carter [this message]
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=2920a713778046808ee4a8c2b12002f2@gmail.com \
--to=yass27106@gmail.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@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