From: Krzysztof Kozlowski <krzk@kernel.org>
To: Wig Cheng <onlywig@gmail.com>, robh@kernel.org
Cc: krzk+dt@kernel.org, conor+dt@kernel.org,
neil.armstrong@linaro.org, heiko@sntech.de,
kever.yang@rock-chips.com, manivannan.sadhasivam@linaro.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: vendor-prefixes: Add Mayqueen name
Date: Fri, 23 May 2025 09:22:31 +0200 [thread overview]
Message-ID: <a8c6efba-103e-4760-9d49-0b3cf7bd1edf@kernel.org> (raw)
In-Reply-To: <20250522163142.3421893-1-onlywig@gmail.com>
On 22/05/2025 18:31, Wig Cheng wrote:
> Mayqueen is a Taiwan-based company primarily focused on the development
> of arm64 development boards and e-paper displays. They will be working on
> mainlining the DTS for their boards and e-paper DRM drivers,
> necessitating the addition of their vendor prefix.
No, "they will" is not "necessitating". I do not see implementing
Conor's comment. Such patch ALWAYS comes with an user in upstream project.
Please version your patches correctly, e.g. use b4 or git format-patch
-vX, and add changelog in cover letter or under '---' of individual
patches describing changes from previous version.
>
> This vendor prefix will be used in upcoming DRM driver patches for their
> e-paper displays, such as the pixpaper-213-c and future models.
>
> Website: https://www.mayqueentech.com
>
> pixpaper-213-c e-paper:
> https://github.com/MayQueenTechCommunity/PIXPAPER-213-C
That's not upstream.
Best regards,
Krzysztof
prev parent reply other threads:[~2025-05-23 7:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 16:31 [PATCH] dt-bindings: vendor-prefixes: Add Mayqueen name Wig Cheng
2025-05-23 7:22 ` Krzysztof Kozlowski [this message]
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=a8c6efba-103e-4760-9d49-0b3cf7bd1edf@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=kever.yang@rock-chips.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=neil.armstrong@linaro.org \
--cc=onlywig@gmail.com \
--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).