From: Conor Dooley <conor@kernel.org>
To: Langyan Ye <yelangyan@huaqin.corp-partner.google.com>
Cc: neil.armstrong@linaro.org, simona@ffwll.ch,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, heiko@sntech.de, mani@kernel.org,
prabhakar.mahadev-lad.rj@bp.renesas.com, dev@kael-k.io,
kever.yang@rock-chips.com, dri-devel@lists.freedesktop.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
dianders@chromium.org
Subject: Re: [PATCH v3 1/3] dt-bindings: vendor: add taiguanck
Date: Mon, 16 Feb 2026 17:49:16 +0000 [thread overview]
Message-ID: <20260216-appendix-recipient-1836ea619cf6@spud> (raw)
In-Reply-To: <20260214085409.3489057-2-yelangyan@huaqin.corp-partner.google.com>
[-- Attachment #1: Type: text/plain, Size: 1214 bytes --]
On Sat, Feb 14, 2026 at 04:54:07PM +0800, Langyan Ye wrote:
> Add the "taiguanck" vendor prefix for Shenzhen Top Group Technology Co., Ltd.
>
> The prefix is derived from the vendor's website domain:
> www.taiguanck.com/en/, which uses "taiguanck" as the primary
This website doesn't exist it seems. I get an ERR_EMPTY_RESPONSE.
> identifier of the company.
>
> Signed-off-by: Langyan Ye <yelangyan@huaqin.corp-partner.google.com>
> ---
> Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/vendor-prefixes.yaml b/Documentation/devicetree/bindings/vendor-prefixes.yaml
> index fc7985f3a549..1856e455f7e6 100644
> --- a/Documentation/devicetree/bindings/vendor-prefixes.yaml
> +++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml
> @@ -1598,6 +1598,8 @@ patternProperties:
> "^synopsys,.*":
> description: Synopsys, Inc. (deprecated, use snps)
> deprecated: true
> + "^taiguanck,.*":
> + description: Shenzhen Top Group Technology Co., Ltd.
> "^taos,.*":
> description: Texas Advanced Optoelectronic Solutions Inc.
> "^tbs,.*":
> --
> 2.34.1
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-02-16 17:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-14 8:54 [PATCH v3 0/3] support for taiguan-xti05101-01a MIPI-DSI panel Langyan Ye
2026-02-14 8:54 ` [PATCH v3 1/3] dt-bindings: vendor: add taiguanck Langyan Ye
2026-02-16 17:49 ` Conor Dooley [this message]
2026-02-18 7:59 ` Krzysztof Kozlowski
2026-02-18 18:12 ` Conor Dooley
2026-02-14 8:54 ` [PATCH v3 2/3] dt-bindings: display: panel: Add compatible for TAIGUAN XTI05101-01A Langyan Ye
2026-02-23 17:58 ` Rob Herring (Arm)
2026-02-14 8:54 ` [PATCH v3 3/3] drm/panel: panel-jadard-jd9365da-h3: support for taiguan-xti05101-01a MIPI-DSI panel Langyan Ye
2026-03-04 16:34 ` neil.armstrong
2026-03-10 13:28 ` [PATCH v3 0/3] " Neil Armstrong
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=20260216-appendix-recipient-1836ea619cf6@spud \
--to=conor@kernel.org \
--cc=conor+dt@kernel.org \
--cc=dev@kael-k.io \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=kever.yang@rock-chips.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mani@kernel.org \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=robh@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
--cc=yelangyan@huaqin.corp-partner.google.com \
/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