linux-kernel - Re: [PATCH v3 2/9] dt-bindings: soc: renesas: Add RZ/G3E variant SYS binding

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250123-conscious-resolute-dog-b3dda7@krzk-bin>
Date: Thu, 23 Jan 2025 08:45:19 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: John Madieu <john.madieu.xa@...renesas.com>
Cc: geert+renesas@...der.be, robh@...nel.org, 
	linux-renesas-soc@...r.kernel.org, devicetree@...r.kernel.org, biju.das.jz@...renesas.com, 
	claudiu.beznea.uj@...renesas.com, conor+dt@...nel.org, john.madieu@...il.com, krzk+dt@...nel.org, 
	linux-kernel@...r.kernel.org, magnus.damm@...il.com
Subject: Re: [PATCH v3 2/9] dt-bindings: soc: renesas: Add RZ/G3E variant SYS
 binding

On Wed, Jan 22, 2025 at 11:39:04AM +0100, John Madieu wrote:
> Add RZ/G3E (R9A09G047) variant to the existing RZ/V2H System
> Controller (SYS) binding as both IPs are compatible.
> 
> They however have different SoC IDs, RZ/G3E has has VSP control Register
> compared to RZ/V2H SYS IP. Hence a new compatible string renesas,r9a09g047-sys
> introduced to handle these differences.
> 
> Signed-off-by: John Madieu <john.madieu.xa@...renesas.com>
> ---
>  .../bindings/soc/renesas/renesas,r9a09g057-sys.yaml          | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
> 

<form letter>
This is a friendly reminder during the review process.

It looks like you received a tag and forgot to add it.

If you do not know the process, here is a short explanation:
Please add Acked-by/Reviewed-by/Tested-by tags when posting new
versions of patchset, under or above your Signed-off-by tag, unless
patch changed significantly (e.g. new properties added to the DT
bindings). Tag is "received", when provided in a message replied to you
on the mailing list. Tools like b4 can help here. However, there's no
need to repost patches *only* to add the tags. The upstream maintainer
will do that for tags received on the version they apply.

Please read:
https://elixir.bootlin.com/linux/v6.12-rc3/source/Documentation/process/submitting-patches.rst#L577

If a tag was not added on purpose, please state why and what changed.
</form letter>

Best regards,
Krzysztof