Re: [PATCH v7 1/5] dt-bindings: crypto: add Rambus CryptoManager Hub

[Krzysztof Kozlowski <krzk@kernel.org>]

On 26/10/2026 20:44, Alex Ousherovitch via B4 Relay wrote:
> From: Alex Ousherovitch <aousherovitch@rambus.com>
> 
> Add device tree binding schema for the Rambus CryptoManager Hub (CMH)
> hardware crypto accelerator.  The binding describes the parent
> SoC-level node with its SIC register region and one queue@N child
> node per mailbox the host owns, each carrying a reg (mailbox instance
> index), an optional interrupt, VCQ ring geometry (rambus,num-slots /
> rambus,slot-stride-bytes) and a rambus,cores affinity list.  Which
> crypto cores are present is discovered from the SIC CORE_ENABLE
> register at probe, not described in the device tree.
> 
> Register the 'rambus' vendor prefix for Rambus Inc.
> 
> Co-developed-by: Saravanakrishnan Krishnamoorthy <skrishnamoorthy@rambus.com>
> Signed-off-by: Saravanakrishnan Krishnamoorthy <skrishnamoorthy@rambus.com>
> Signed-off-by: Alex Ousherovitch <aousherovitch@rambus.com>

Why is this sent multiple times?

b4 diff '<20261026-cmh-b4-a-v7-v7-1-500a83faf500@rambus.com>'
Looking up 20261026-cmh-b4-a-v7-v7-1-500a83faf500@rambus.com
Checking for older revisions
Grabbing search results from lore.kernel.org
---
Analyzing 8 messages in the thread
Could not find lower series to compare against.

And both variants are present in Patchwork, so not sure what you want us
to do here.

Best regards,
Krzysztof