Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Zakariya Hadrami via B4 Relay" <devnull+zkh1.proton.me@kernel.org>
Cc: devicetree@vger.kernel.org, linux-watchdog@vger.kernel.org,
	robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH 4/5] dt-bindings: arm: mediatek: Add MT8127 Amazon ford
Date: Wed, 17 Jun 2026 02:29:02 +0000	[thread overview]
Message-ID: <20260617022902.F2C441F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260617-mt8127-amazon-ford-basic-v1-4-d02ad15ac359@proton.me>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The device tree compatible block for `amazon,ford` is incorrectly sorted. The file specifies that entries should be sorted by SoC compatible and then alphabetically by board compatible. Because `amazon,ford` and `mediatek,mt8127-moose` share the same SoC compatible (`mediatek,mt8127`), `amazon,ford` should be placed before `mediatek,mt8127-moose`.
--

commit 5d4dd6329b44b144dcfbe78c4a1cf82524b51ef6
Author: Zakariya Hadrami <zkh1@proton.me>

dt-bindings: arm: mediatek: Add MT8127 Amazon ford

This commit adds the device tree binding for the Amazon ford tablet based
on the MediaTek MT8127 SoC.

> diff --git a/Documentation/devicetree/bindings/arm/mediatek.yaml b/Documentation/devicetree/bindings/arm/mediatek.yaml
> index 382d0eb4d0af6..5ddc79689df91 100644
> --- a/Documentation/devicetree/bindings/arm/mediatek.yaml
> +++ b/Documentation/devicetree/bindings/arm/mediatek.yaml
> @@ -124,6 +124,10 @@ properties:
>            - enum:
>                - mediatek,mt8127-moose
>            - const: mediatek,mt8127
> +      - items:
> +          - enum:
> +              - amazon,ford
> +          - const: mediatek,mt8127

[Severity: Low]
This isn't a bug, but should the amazon,ford board compatible block be
inserted alphabetically before mediatek,mt8127-moose? Since both share the
mediatek,mt8127 SoC compatible, sorting alphabetically by the board
compatible would usually place amazon,ford first.

>        - items:
>            - enum:
>                - mediatek,mt8135-evbp1

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260617-mt8127-amazon-ford-basic-v1-0-d02ad15ac359@proton.me?part=4

  reply	other threads:[~2026-06-17  2:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-17  2:20 [PATCH 0/5] ARM: Basic support for Amazon ford tablet (MT8127) Zakariya Hadrami via B4 Relay
2026-06-17  2:20 ` [PATCH 1/5] ARM: dts: mediatek: mt8127: Fix indentation error Zakariya Hadrami via B4 Relay
2026-06-17  2:20 ` [PATCH 2/5] ARM: dts: mediatek: mt8127: Add watchdog support Zakariya Hadrami via B4 Relay
2026-06-17  2:30   ` sashiko-bot
2026-06-17  2:20 ` [PATCH 3/5] ARM: dts: mediatek: Add basic support for Amazon ford board Zakariya Hadrami via B4 Relay
2026-06-17  2:20 ` [PATCH 4/5] dt-bindings: arm: mediatek: Add MT8127 Amazon ford Zakariya Hadrami via B4 Relay
2026-06-17  2:29   ` sashiko-bot [this message]
2026-06-17  2:20 ` [PATCH 5/5] dt-bindings: watchdog: mediatek: Add MT8127 Zakariya Hadrami via B4 Relay

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=20260617022902.F2C441F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=devnull+zkh1.proton.me@kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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