devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wig Cheng <onlywig@gmail.com>
To: conor@kernel.org
Cc: robh@kernel.org, onlywig@gmail.com, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: vendor-prefixes: rename nutsboard to mayqueen
Date: Thu, 22 May 2025 23:58:08 +0800	[thread overview]
Message-ID: <20250522155810.3414273-1-onlywig@gmail.com> (raw)
In-Reply-To: <20250522-difficult-yummy-84376495b270@spud>

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

  parent reply	other threads:[~2025-05-22 15:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-22 15:22 [PATCH] dt-bindings: vendor-prefixes: rename nutsboard to mayqueen Wig Cheng
2025-05-22 15:30 ` Conor Dooley
2025-05-22 15:31   ` Conor Dooley
2025-05-22 15:50   ` Wig Cheng
2025-05-22 15:58   ` Wig Cheng [this message]
2025-05-23 15:49     ` Conor Dooley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250522155810.3414273-1-onlywig@gmail.com \
    --to=onlywig@gmail.com \
    --cc=conor@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).