From: sashiko-bot@kernel.org
To: Quchaosheng <quchaosheng000406@163.com>
Cc: conor+dt@kernel.org, robh@kernel.org,
"Oleksij Rempel" <o.rempel@pengutronix.de>,
devicetree@vger.kernel.org,
"Vincent Mailhol" <mailhol@kernel.org>,
linux-can@vger.kernel.org,
"Marc Kleine-Budde" <mkl@pengutronix.de>,
"Oliver Hartkopp" <socketcan@hartkopp.net>
Subject: Re: [PATCH v2] dt-bindings: net: can: convert ifi_canfd to DT schema
Date: Mon, 14 Sep 2026 01:45:30 +0000 [thread overview]
Message-ID: <20260914014530.AA5E91F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260914013745.394514-1-quchaosheng000406@163.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Incorrect use of `additionalProperties: false` when inheriting from a common schema via `$ref`, which improperly blocks inherited properties.
--
commit 471062b3f0e20cbfb084fbd8547c9d66999316e1
Author: Quchaosheng <quchaosheng000406@163.com>
dt-bindings: net: can: convert ifi_canfd to DT schema
Convert the IFI CAN-FD controller binding from free-form text to DT schema,
and reference the common can-controller.yaml schema.
> diff --git a/Documentation/devicetree/bindings/net/can/ifi,canfd.yaml b/Documentation/devicetree/bindings/net/can/ifi,canfd.yaml
> new file mode 100644
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/net/can/ifi,canfd.yaml
[ ... ]
> +allOf:
> + - $ref: can-controller.yaml#
> +
> +properties:
[ ... ]
> +required:
> + - compatible
> + - reg
> + - interrupts
> +
> +additionalProperties: false
[Severity: Medium]
Does using additionalProperties: false here conflict with the $ref to
can-controller.yaml#?
When referencing another schema via allOf, using additionalProperties: false
strictly forbids any properties not defined in the local file. This will cause
validation to fail if a device tree node includes standard CAN controller
properties like termination-gpios that are inherited from can-controller.yaml.
Should this be unevaluatedProperties: false instead, to allow the properties
defined in the referenced common schema?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260914013745.394514-1-quchaosheng000406@163.com?part=1
next prev parent reply other threads:[~2026-09-14 1:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 1:37 [PATCH v2] dt-bindings: net: can: convert ifi_canfd to DT schema Quchaosheng
2026-09-14 1:45 ` sashiko-bot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-09-14 1:36 Quchaosheng
2026-09-14 1:45 ` 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=20260914014530.AA5E91F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=mailhol@kernel.org \
--cc=mkl@pengutronix.de \
--cc=o.rempel@pengutronix.de \
--cc=quchaosheng000406@163.com \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=socketcan@hartkopp.net \
/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