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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAK+owojEmcW7S8oFFjmmeT1uHn2Hyb9=16GDP2QLQ+DAEwtoPg@mail.gmail.com>
Date: Thu, 10 Jul 2025 16:57:52 +0200
From: Stefano Radaelli <stefano.radaelli21@...il.com>
To: Krzysztof Kozlowski <krzk@...nel.org>
Cc: devicetree@...r.kernel.org, linux-kernel@...r.kernel.org, 
	Nishanth Menon <nm@...com>, Vignesh Raghavendra <vigneshr@...com>, Tero Kristo <kristo@...nel.org>, 
	Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>, 
	linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v2 1/3] dt-bindings: arm: ti: Add bindings for Variscite VAR-SOM-AM62P

On 10/07/2025 16:42, Krzysztof Kozlowski wrote:
> There are no such compatibles. There are:
>
> variscite,var-som-mx93
> variscite,var-som-mx8mn
>
> and others with exact format how I asked - var-som-<processor>.
>

You are absolutely correct, and I apologize for the confusion.
I was incorrectly referring to our internal kernel tree instead of
checking the mainline kernel compatibles.

Thank you for your patience in correcting me.
I will follow your advice and use the proper mainline format
"var-som-<processor>" for consistency with the existing Variscite compatibles
already present in mainline, rather than our internal naming convention.

I will update the patch accordingly.

Best regards,
Stefano

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ