From: Rob Herring <robh@kernel.org>
To: sashiko-reviews@lists.linux.dev
Cc: Alex Ousherovitch <aousherovitch@rambus.com>,
Saravanakrishnan Krishnamoorthy <skrishnamoorthy@rambus.com>,
Joel Wittenauer <Joel.Wittenauer@cryptography.com>,
Thi Nguyen <thin@rambus.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
linux-crypto@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v8 1/5] dt-bindings: crypto: add Rambus CryptoManager Hub
Date: Thu, 12 Nov 2026 16:28:27 -0600 [thread overview]
Message-ID: <20261112222827.GA1685895-robh@kernel.org> (raw)
In-Reply-To: <sashiko-outbox-207462@kernel.org>
On Tue, Nov 10, 2026 at 05:20:21PM +0000, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential
> issue to consider:
> - [Medium] dt-bindings: crypto: rambus,cmh-v1030: invalid unit suffix
> and $ref on rambus,slot-stride-bytes
> --
>
> commit fe48437ab6a40e215371f9ad1c5f69cf88124d19
> Author: Alex Ousherovitch <aousherovitch@rambus.com>
>
> dt-bindings: crypto: add Rambus CryptoManager Hub
>
> This commit adds the device tree binding schema for the Rambus
> CryptoManager Hub hardware crypto accelerator and registers the rambus
> vendor prefix.
>
> > diff --git a/Documentation/devicetree/bindings/crypto/rambus,cmh-v1030.yaml b/Documentation/devicetree/bindings/crypto/rambus,cmh-v1030.yaml
> > new file mode 100644
> > index 0000000000000..eef82c2d71794
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/crypto/rambus,cmh-v1030.yaml
> > @@ -0,0 +1,145 @@
>
> [ ... ]
>
> > + rambus,slot-stride-bytes:
> > + $ref: /schemas/types.yaml#/definitions/uint32
> > + enum: [512, 1024]
> > + default: 512
> > + description:
> > + Stride in bytes between consecutive VCQ ring slots for this
> > + mailbox's command queue. Like rambus,num-slots this is a
> > + per-board host-memory ring geometry, not derived from the
> > + compatible. A slot must hold a complete command sequence,
> > + which needs at least 512 bytes.
>
> [Severity: Medium]
> Does rambus,slot-stride-bytes cause make dt_binding_check to fail?
>
> In dtschema (meta-schemas/vendor-props.yaml), the -bytes unit suffix is
> deprecated and disallowed on vendor properties, and properties using a
> standard unit suffix already have their uint32 type assigned by the core
> schema and must not specify $ref: /schemas/types.yaml#/definitions/uint32.
That's got to be the worst hallucination I've seen from sashiko. There
is no -bytes suffix.
Rob
next prev parent reply other threads:[~2026-11-12 22:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 16:52 [PATCH v8 0/5] crypto: cmh - add Rambus CryptoManager Hub core driver and AES Alex Ousherovitch via B4 Relay
2026-11-10 16:52 ` [PATCH v8 1/5] dt-bindings: crypto: add Rambus CryptoManager Hub Alex Ousherovitch via B4 Relay
2026-11-10 17:20 ` sashiko-bot
2026-11-12 22:28 ` Rob Herring [this message]
2026-11-12 22:29 ` Rob Herring (Arm)
2026-11-10 16:52 ` [PATCH v8 2/5] crypto: cmh - add core platform driver Alex Ousherovitch via B4 Relay
2026-11-10 17:50 ` sashiko-bot
2026-11-10 16:52 ` [PATCH v8 3/5] crypto: cmh - add key/datastore infrastructure Alex Ousherovitch via B4 Relay
2026-11-10 16:52 ` [PATCH v8 4/5] crypto: cmh - add AES skcipher/aead/cmac Alex Ousherovitch via B4 Relay
2026-11-10 18:18 ` sashiko-bot
2026-11-10 16:52 ` [PATCH v8 5/5] MAINTAINERS: add Rambus CryptoManager Hub (CMH) Alex Ousherovitch 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=20261112222827.GA1685895-robh@kernel.org \
--to=robh@kernel.org \
--cc=Joel.Wittenauer@cryptography.com \
--cc=aousherovitch@rambus.com \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=krzk+dt@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=skhan@linuxfoundation.org \
--cc=skrishnamoorthy@rambus.com \
--cc=thin@rambus.com \
/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