From: sashiko-bot@kernel.org
To: Frank.Li@oss.nxp.com
Cc: imx@lists.linux.dev, devicetree@vger.kernel.org, robh@kernel.org,
Frank.Li@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v4 1/4] dt-bindings: remoteproc: imx_rproc: document memory-region-names to avoid hidden ABI
Date: Thu, 17 Sep 2026 18:28:16 +0000 [thread overview]
Message-ID: <20260917182816.CB5C91F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260917-memory-region-name-v4-1-260755920ebf@nxp.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] dt-bindings: erroneous regex pattern allows invalid region names
--
commit 3fcb4e5cb8e128ab899161b1bbe809e6627ba8ca
Author: Laurentiu Mihalcea <laurentiu.mihalcea@nxp.com>
dt-bindings: remoteproc: imx_rproc: document memory-region-names to avoid hidden ABI
This commit documents the optional memory-region-names property for the i.MX
remoteproc driver. It explicitly identifies expected memory regions to avoid
relying on memory node names as a hidden ABI.
Link: https://lore.kernel.org/imx/a3602ef8-2b77-4cc3-adef-2c4cba08a5d9@nabladev.com/ [1]
Link: https://lore.kernel.org/imx/alexXTYQHUs76J7v@SMW015318/T/#mb9dc709ff3adc24d9db6d30c973f37b580f6f1f9 [2]
> diff --git a/Documentation/devicetree/bindings/remoteproc/fsl,imx-rproc.yaml b/Documentation/devicetree/bindings/remoteproc/fsl,imx-rproc.yaml
> index c18f71b648890..5d98d21035f8c 100644
> --- a/Documentation/devicetree/bindings/remoteproc/fsl,imx-rproc.yaml
> +++ b/Documentation/devicetree/bindings/remoteproc/fsl,imx-rproc.yaml
> @@ -62,6 +62,15 @@ properties:
> minItems: 1
> maxItems: 32
>
> + memory-region-names:
> + minItems: 1
> + maxItems: 32
> + items:
> + anyOf:
> + - const: rsc-table
> + - pattern: "^vdev[0-9]+(buffer|vring[0-9])+$"
[Severity: Low]
Does this regex pattern correctly validate the memory region names?
By applying the + quantifier to the capture group (buffer|vring[0-9]) rather
than the digit class [0-9], this allows repeated suffixes like
vdev0bufferbuffer or vdev0vring0vring1 to pass schema validation.
It also restricts the vring index to a single digit, so vdev0vring10 would fail.
Should the + be moved to the digit class, such as
"^vdev[0-9]+(buffer|vring[0-9]+)$"?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260917-memory-region-name-v4-0-260755920ebf@nxp.com?part=1
next prev parent reply other threads:[~2026-09-17 18:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 18:19 [PATCH v4 0/4] remoteproc: imx_rpoc: use memory-region-names to avoid hidden ABI Frank.Li
2026-09-17 18:19 ` [PATCH v4 1/4] dt-bindings: remoteproc: imx_rproc: document " Frank.Li
2026-09-17 18:28 ` sashiko-bot [this message]
2026-10-09 3:16 ` Peng Fan
2026-09-17 18:19 ` [PATCH v4 2/4] remoteproc: imx_rpoc: use " Frank.Li
2026-10-09 3:17 ` Peng Fan
2026-09-17 18:19 ` [PATCH v4 3/4] arm64: dts: freescale: imx95-15x15-frdm: remove some rmem regions Frank.Li
2026-09-17 18:26 ` sashiko-bot
2026-10-09 3:19 ` Peng Fan
2026-09-17 18:19 ` [PATCH v4 4/4] arm64: dts: freescale: add DT overlay for MX95-15x15-FRDM RPMSG usage Frank.Li
2026-10-09 3:21 ` Peng Fan
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=20260917182816.CB5C91F00893@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=Frank.Li@oss.nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=imx@lists.linux.dev \
--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.