From: sashiko-bot@kernel.org
To: "GUO Ren (XuanTie)" <guoren@kernel.org>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v2] dt-bindings: vendor-prefixes: Add Xuantie Semiconductor
Date: Mon, 17 Aug 2026 09:51:02 +0000 [thread overview]
Message-ID: <20260817095102.8B4CC1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260817-xt_vendor_v2-v2-1-8d4eed65a533@kernel.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Introduces a duplicate and unused vendor prefix (`xuantie`) for a vendor that already uses the established `thead` prefix.
--
--- Patch [1]: [PATCH v2] dt-bindings: vendor-prefixes: Add Xuantie Semiconductor ---
commit 9230660a7e40e4df99ae36ef91b16bfb20d60e44
Author: GUO Ren (XuanTie) <guoren@kernel.org>
dt-bindings: vendor-prefixes: Add Xuantie Semiconductor
This commit adds xuantie as a new vendor prefix for Shanghai Xuantie
Semiconductor Technology Co., Ltd. in the devicetree bindings.
> diff --git a/Documentation/devicetree/bindings/vendor-prefixes.yaml b/Documentation/devicetree/bindings/vendor-prefixes.yaml
> --- a/Documentation/devicetree/bindings/vendor-prefixes.yaml
> +++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml
[ ... ]
> @@ -1905,6 +1905,8 @@ patternProperties:
> description: Xilinx
> "^xnano,.*":
> description: Xnano
> + "^xuantie,.*":
> + description: Shanghai Xuantie Semiconductor Technology Co., Ltd.
[Severity: Low]
Is this vendor prefix redundant given the established thead prefix?
The kernel already relies heavily on the thead prefix for T-Head/XuanTie
processor IPs (like thead,c906, thead,th1520, and thead,c920). Adding
multiple vendor prefixes for the same company fragments the devicetree
namespace.
Also, since the actual compatible strings using this prefix were removed
in V2 (as noted in the changelog), the xuantie prefix is currently completely
unused. Would it be better to drop this patch entirely and continue using
the established thead prefix?
> "^xunlong,.*":
> description: Shenzhen Xunlong Software CO.,Limited
> "^xylon,.*":
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260817-xt_vendor_v2-v2-1-8d4eed65a533@kernel.org?part=1
prev parent reply other threads:[~2026-08-17 9:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 9:46 [PATCH v2] dt-bindings: vendor-prefixes: Add Xuantie Semiconductor GUO Ren (XuanTie)
2026-08-17 9:51 ` sashiko-bot [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=20260817095102.8B4CC1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=guoren@kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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