linux-kernel - Re: [PATCH] dt-bindings: vendor-prefixes: rename nutsboard to mayqueen

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250522155027.3412993-1-onlywig@gmail.com>
Date: Thu, 22 May 2025 23:50:06 +0800
From: Wig Cheng <onlywig@...il.com>
To: robh@...nel.org
Cc: conor@...nel.org,
	onlywig@...il.com,
	devicetree@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] dt-bindings: vendor-prefixes: rename nutsboard to mayqueen

Hi Rob,

Thanks for the clarification and guidance on the rules.

I believe the nutsboard prefix is no longer in use, as the related device tree files were removed from mainline starting from kernel 6.1. Additionally, we have informed all our customers to upgrade to the new hardware. However, I appreciate your explanation and will mark the old prefix as deprecated instead of removing it.

I also have a question regarding the new prefix. The reason for this change is that we’ve developed a DRM driver, and the platform device in the driver uses a compatible string referring to the device tree. Without a vendor prefix, I’m unable to upstream the DRM driver because it lacks a valid compatible string.

How should this situation be handled? Is it acceptable to introduce the new vendor prefix first for this purpose?

Product page:
https://github.com/MayQueenTechCommunity/PIXPAPER-213-C

Best regards,  
Wig