From: Michal Simek <michal.simek@amd.com>
To: Pufan Jin <2254650260@qq.com>, Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Rob Herring <robh@kernel.org>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, andrew@lunn.ch
Subject: Re: [PATCH v2 1/3] dt-bindings: vendor-prefixes: Add ALINX vendor prefix
Date: Mon, 12 Oct 2026 14:41:30 +0200 [thread overview]
Message-ID: <df09cefa-6c7c-4b5c-8215-1a1419fbbe9f@amd.com> (raw)
In-Reply-To: <tencent_C77DAF0026980C137B8C46907F855FC9E506@qq.com>
On 10/5/26 19:30, Pufan Jin wrote:
> Add vendor prefix for ALINX (Shanghai Xin'yi Electronics Technology
> Co., Ltd.).
>
> Signed-off-by: Pufan Jin <2254650260@qq.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 ba2002969..97e7ef340 100644
> --- a/Documentation/devicetree/bindings/vendor-prefixes.yaml
> +++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml
> @@ -90,6 +90,8 @@ patternProperties:
> description: AlgolTek, Inc.
> "^alientek,.*":
> description: Guangzhou Xingyi Intelligent Technology Co., Ltd.
> + "^alinx,.*":
> + description: Shanghai Xin'yi Electronics Technology Co., Ltd. (ALINX)
> "^allegro,.*":
> description: Allegro DVT
> "^allegromicro,.*":
Another separate thread. Ignoring.
M
next prev parent reply other threads:[~2026-10-12 12:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20261005173039.707304-1-2254650260@qq.com>
2026-10-05 17:30 ` Pufan Jin
2026-10-12 12:41 ` Michal Simek [this message]
2026-10-05 17:30 ` [PATCH v2 2/3] dt-bindings: soc: xilinx: Add ALINX EdgeBoard FZ3A Pufan Jin
2026-10-05 17:30 ` [PATCH v2 3/3] arm64: zynqmp: " Pufan Jin
[not found] <20261005173308.710986-1-2254650260@qq.com>
2026-10-05 17:33 ` [PATCH v2 1/3] dt-bindings: vendor-prefixes: Add ALINX vendor prefix Pufan Jin
2026-10-07 10:35 ` Conor Dooley
2026-10-07 17:36 ` Pufan Jin
2026-10-08 7:25 ` 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=df09cefa-6c7c-4b5c-8215-1a1419fbbe9f@amd.com \
--to=michal.simek@amd.com \
--cc=2254650260@qq.com \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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
all inboxes | Powered by JetHome®