From: sashiko-bot@kernel.org
To: "Joy Zou" <joy.zou@oss.nxp.com>
Cc: devicetree@vger.kernel.org, imx@lists.linux.dev, robh@kernel.org,
conor+dt@kernel.org, Frank.Li@kernel.org
Subject: Re: [PATCH v2 1/3] dt-bindings: arm: fsl: add i.MX937 FRDM board
Date: Fri, 20 Nov 2026 11:12:27 +0000 [thread overview]
Message-ID: <sashiko-outbox-224997@kernel.org> (raw)
In-Reply-To: <20261120-b4-imx937-frdm-v2-1-5e27ceec02df@oss.nxp.com>
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Low] dt-bindings: arm: fsl: commit log says fsl,imx952-frdm instead
of fsl,imx952
--
commit 42f4f6eed8a4edf16ac9cee36f90e0ee040c6e5d
Author: Joy Zou <joy.zou@oss.nxp.com>
dt-bindings: arm: fsl: add i.MX937 FRDM board
This commit adds the devicetree binding for the NXP i.MX937 FRDM board,
including the fsl,imx952 fallback SoC compatible string.
> Add the fsl,imx952-frdm compatible string to reuse the existing
> support and avoid code duplication.
[Severity: Low]
This isn't a bug, but the commit message mentions fsl,imx952-frdm instead
of the fsl,imx952 fallback compatible string added by the patch.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261120-b4-imx937-frdm-v2-0-5e27ceec02df@oss.nxp.com?part=1
next prev parent reply other threads:[~2026-11-20 11:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-20 11:09 [PATCH v2 0/3] arm64: dts: freescale: add i.MX937 FRDM board support Joy Zou
2026-11-20 11:09 ` [PATCH v2 1/3] dt-bindings: arm: fsl: add i.MX937 FRDM board Joy Zou
2026-11-20 11:12 ` sashiko-bot [this message]
2026-11-20 17:11 ` Frank Li
2026-11-20 11:09 ` [PATCH v2 2/3] arm64: dts: imx952-frdm: model CAN/GPIO selector as gpio-mux Joy Zou
2026-11-20 11:09 ` [PATCH v2 3/3] arm64: dts: freescale: add i.MX937 FRDM board support Joy Zou
2026-11-20 11:11 ` sashiko-bot
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-224997@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=joy.zou@oss.nxp.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.