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: <c8a16b30-569a-4266-9e2c-86be348afa86@kernel.org>
Date: Sat, 12 Jul 2025 18:45:56 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Magnus Damm <damm@...nsource.se>, linux-renesas-soc@...r.kernel.org
Cc: robh@...nel.org, geert+renesas@...der.be, devicetree@...r.kernel.org,
 conor+dt@...nel.org, linux-kernel@...r.kernel.org,
 wsa+renesas@...g-engineering.com, sergei.shtylyov@...il.com,
 p.zabel@...gutronix.de
Subject: Re: [PATCH v2 1/4] dt-bindings: memory-controllers: renesas,rpc-if:
 Add RZ/A1 and RZ/A2 compat strings

On 12/07/2025 15:39, Magnus Damm wrote:
> From: Magnus Damm <damm@...nsource.se>
> 
> Add RZ/A1 and RZ/A2 compat strings for the renesas rpc-if device.
> 
> Signed-off-by: Magnus Damm <damm@...nsource.se>
> ---
> 
>  Changes since v1:
>  - Moved RZ/A to top of RZ
> 
>  Applies to next-20250710
> 
>  Documentation/devicetree/bindings/memory-controllers/renesas,rpc-if.yaml |    5 +++++
>  1 file changed, 5 insertions(+)
> 
> --- 0001/Documentation/devicetree/bindings/memory-controllers/renesas,rpc-if.yaml
> +++ work/Documentation/devicetree/bindings/memory-controllers/renesas,rpc-if.yaml	2025-07-11 04:50:41.505855241 +0900
> @@ -50,6 +50,11 @@ properties:
>  
>        - items:
>            - enum:
> +	      - renesas,r7s72100-rpc-if       # RZ/A1H
> +	      - renesas,r7s9210-rpc-if        # RZ/A2M

Still not tested.

You got extensive guideline from me last time. You just replied (in
private!) that you are not going to install dtschema and test it.

Fine if you send correct code.

Not fine if you write buggy code. And this is obviously the case here as
easily visible in the diff above - borken indentation.

Please read carefully previous instructions.

Best regards,
Krzysztof

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ