From: sashiko-bot@kernel.org
To: "Val Packett" <val@packett.cool>
Cc: devicetree@vger.kernel.org, linux-rtc@vger.kernel.org,
robh@kernel.org, conor+dt@kernel.org,
"Alexandre Belloni" <alexandre.belloni@bootlin.com>
Subject: Re: [PATCH 1/5] dt-bindings: arm: qcom: Document Microsoft Surface Pro X
Date: Wed, 04 Nov 2026 07:10:39 +0000 [thread overview]
Message-ID: <sashiko-outbox-196779@kernel.org> (raw)
In-Reply-To: <20261104070441.74127-2-val@packett.cool>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] dt-bindings: arm: qcom: commit message duplicates carina and omits caspar
--
commit c0354ee6a701cd3d9a5f7b5512415336071339b5
Author: Val Packett <val@packett.cool>
dt-bindings: arm: qcom: Document Microsoft Surface Pro X
This commit replaces the generic microsoft,surface-prox compatible string in
Documentation/devicetree/bindings/arm/qcom.yaml with three model-specific
compatible strings for the Surface Pro X variants.
> dt-bindings: arm: qcom: Document Microsoft Surface Pro X
>
> The Surface Pro X tablet was listed as a single generic compatible in
> dt-bindings, but a device tree using it has not landed upstream.
>
> Replace it with three model-specific compatibles:
> * microsoft,cambria for the orginal SQ1 model (with cellular)
> * microsoft,carina for the Wi-Fi-only (SQ1) model
> * microsoft,carina for the SQ2 refresh
>
> Signed-off-by: Val Packett <val@packett.cool>
>
> diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml b/Documentation/devicetree/bindings/arm/qcom.yaml
> index 121ca557ce1ef..74f46697a363f 100644
> --- a/Documentation/devicetree/bindings/arm/qcom.yaml
> +++ b/Documentation/devicetree/bindings/arm/qcom.yaml
> @@ -925,7 +925,9 @@ properties:
> - items:
> - enum:
> - lenovo,flex-5g
> - - microsoft,surface-prox
> + - microsoft,cambria
> + - microsoft,carina
> + - microsoft,caspar
[Severity: Low]
In Documentation/devicetree/bindings/arm/qcom.yaml under
properties.compatible, the schema adds microsoft,cambria, microsoft,carina,
and microsoft,caspar, but the commit message lists microsoft,carina twice
(for both the Wi-Fi-only SQ1 model and the SQ2 refresh) and omits
microsoft,caspar.
Should the Wi-Fi-only (SQ1) entry in the commit description say
microsoft,caspar instead of microsoft,carina?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261104070441.74127-1-val@packett.cool?part=1
next prev parent reply other threads:[~2026-11-04 7:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 7:04 [PATCH 0/5] Add support for the Microsoft Surface Pro X Val Packett
2026-11-04 7:04 ` [PATCH 1/5] dt-bindings: arm: qcom: Document " Val Packett
2026-11-04 7:10 ` sashiko-bot [this message]
2026-11-04 7:04 ` [PATCH 2/5] arm64: dts: qcom: sc8180x: Add " Val Packett
2026-11-04 7:22 ` sashiko-bot
2026-11-04 8:36 ` Konrad Dybcio
2026-11-04 9:05 ` Val Packett
2026-11-04 7:04 ` [PATCH 3/5] firmware: qcom: scm: Allow QSEECOM on the " Val Packett
2026-11-04 7:04 ` [PATCH 4/5] rtc: Add basic support for RTC via Surface System Aggregator Module Val Packett
2026-11-04 7:04 ` [PATCH 5/5] platform/surface: aggregator_registry: Add support for Surface Pro X Val Packett
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=sashiko-outbox-196779@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=val@packett.cool \
/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