linux-kernel - Re: [PATCH v2 3/3] riscv: dts: sophgo: add zfh for sg2042

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: <CAN=L63o=wuv-7a1U4W-=mee+JAWhmvYMDsqkckYV3zYYaDTPnQ@mail.gmail.com>
Date: Wed, 21 May 2025 18:12:15 +0200
From: Alejandro Enrique <alejandroe1@...tab.com>
To: Johan Hovold <johan@...nel.org>
Cc: Conor Dooley <conor@...nel.org>, Rob Herring <robh@...nel.org>, 
	Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>, linux-kernel@...r.kernel.org, 
	devicetree@...r.kernel.org
Subject: Re: [PATCH v2 3/3] riscv: dts: sophgo: add zfh for sg2042

On Mon, May 19, 2025 at 2:59 PM Johan Hovold <johan@...nel.org> wrote:
>
> We still want a new compatible string for the new device. Depending on
> how similar these products are it may be possible to avoid adding a new
> entry to the driver for now by specifying a fallback compatible, for
> example, to neo-m8:
>
>         compatible = "u-blox,neo-m9", "u-blox,neo-m8";
>
> This would then need to be encoded in the binding.

OK, thanks. I will submit a v2 removing the new entry from the driver
and modifying the binding to permit the fallback.