dt-bindings: vendor-prefixes: rename nutsboard to mayqueen

The company behind "nutsboard" has been renamed to "mayqueen". Update the vendor prefix accordingly to reflect the new name.

Website: https://www.mayqueentech.com

---
 Documentation/devicetree/bindings/vendor-prefixes.yaml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

index 5d2a7a8d3ac6..ee1dfb7aa64f 100644
@@ -916,6 +916,8 @@ patternProperties:
     description: Maxim Integrated Products
   "^maxlinear,.*":
     description: MaxLinear Inc.
+  "^mayqueen,.*":
+    description: Mayqueen Technologies Ltd.
   "^mbvl,.*":
     description: Mobiveil Inc.
   "^mcube,.*":

@@ -1084,8 +1086,6 @@ patternProperties:
   "^numonyx,.*":
     description: Numonyx (deprecated, use micron)
     deprecated: true
-  "^nutsboard,.*":
-    description: NutsBoard
   "^nuvoton,.*":
     description: Nuvoton Technology Corporation
   "^nvd,.*":

2.43.0

Whatever about adding a new name, the old name should not be deleted since it has users - maybe it can be marked deprecated.

Additionally, the new name should come with a user, or a link to a user in another project (e.g. u-boot)

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

Hi Conor,

Apologies for the typo. It's been a while since I last used git send-mail.

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

Wig

An additional piece of guidance, please wrap lines in your emails.

grepping the tree disagrees with yout, there's a board still in the tree.

A new company can have a new prefix, this patch adding it should come with the drm device binding that uses it.