From: Harrison Vanderbyl <harrison.vanderbyl@gmail.com>
To: konrad.dybcio@oss.qualcomm.com
Cc: andersson@kernel.org, bentiss@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, dmitry.baryshkov@oss.qualcomm.com,
harrison.vanderbyl@gmail.com, jikos@kernel.org,
konradybcio@kernel.org, krzk+dt@kernel.org,
linux-arm-msm@vger.kernel.org, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v3 2/2] arm64: dts: qcom: Add Microsoft Surface Pro 12in
Date: Tue, 9 Jun 2026 21:04:29 +1000 [thread overview]
Message-ID: <20260609110429.11427-1-harrison.vanderbyl@gmail.com> (raw)
In-Reply-To: <4ced3207-a132-4ec5-a0eb-79f75f5cb4bb@oss.qualcomm.com>
On 6/9/26 11:30 AM, Konrad Dybcio wrote:
> Because we'd put the subnodes for devices under the 'status' line (DTC
> enforces that), please move the comment below as well
Will do,
> Or since it's @28, perhaps it's just nxp,nxp-nci-i2c and it could work
> for you ootb?
Unfortunately for me, the device/antenna is not present on the consumer version,
I was able to confirm this during a speaker replacement.
> Please align the <s (or is it my mail client playing tricks on me?)
The alignment changes depending on what text editor I copy paste this section into.
I have them aligned the same as the other device trees are aligned though.
next prev parent reply other threads:[~2026-06-09 11:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 1:16 [PATCH v3 0/2] Add support for Microsoft Surface Pro 12in Harrison Vanderbyl
2026-05-29 1:16 ` [PATCH v3 1/2] hid: Pen battery quirk for " Harrison Vanderbyl
2026-05-29 1:16 ` [PATCH v3 2/2] arm64: dts: qcom: Add Microsoft " Harrison Vanderbyl
2026-05-29 2:15 ` sashiko-bot
2026-06-09 9:30 ` Konrad Dybcio
2026-06-09 11:04 ` Harrison Vanderbyl [this message]
2026-06-09 12:06 ` Konrad Dybcio
2026-06-01 18:18 ` (subset) [PATCH v3 0/2] Add support for " Benjamin Tissoires
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=20260609110429.11427-1-harrison.vanderbyl@gmail.com \
--to=harrison.vanderbyl@gmail.com \
--cc=andersson@kernel.org \
--cc=bentiss@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=jikos@kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-input@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