From: Krzysztof Kozlowski <krzk@kernel.org>
To: Guo Ren <guoren@kernel.org>, robh@kernel.org
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, robh+dt@kernel.org,
conor.dooley@microchip.com
Subject: Re: [PATCH 1/2] dt-bindings: vendor-prefixes: Add Xuantie Semiconductor
Date: Mon, 17 Aug 2026 08:08:52 +0200 [thread overview]
Message-ID: <bf81034d-7768-40f3-b078-e17ea3a2e665@kernel.org> (raw)
In-Reply-To: <20260815015722.1736831-2-guoren@kernel.org>
On 15/08/2026 03:57, Guo Ren wrote:
> From: "GUO Ren (XuanTie)" <guoren@kernel.org>
>
> Add the xuantie vendor prefix for Shanghai Xuantie Semiconductor
> Technology Co., Ltd., which provides the XuanTie processor IP.
>
> The vendor information is available from the Xuantie declaration
> pagei [1].
>
> [1]: https://www.xrvm.com/declaration
>
> Cc: Rob Herring <robh+dt@kernel.org>
> Cc: devicetree <devicetree@vger.kernel.org>
Please drop the autogenerated scripts/get_maintainer.pl CC-entries from
commit msg. There is no single need to store automated output of
get_maintainers.pl in the git log. It can be easily re-created at any
given time, thus its presence in the git history is redundant and
obfuscates the log.
If you need it for your own patch management purposes, keep it under the
--- separator.
> Signed-off-by: GUO Ren (XuanTie) <guoren@kernel.org>
> ---
> Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
Anyway odd cc-list.
Please use scripts/get_maintainers.pl to get a list of necessary people
and lists to CC (and consider --no-git-fallback argument, so you will
not CC people just because they made one commit years ago). It might
happen, that command when run on an older kernel, gives you outdated
entries. Therefore please be sure you base your patches on recent Linux
kernel.
Tools like b4 or scripts/get_maintainer.pl provide you proper list of
people, so fix your workflow. Tools might also fail if you work on some
ancient tree (don't, instead use mainline) or work on fork of kernel
(don't, instead use mainline). Just use b4 and everything should be
fine, although remember about `b4 prep --auto-to-cc` if you added new
patches to the patchset.
Best regards,
Krzysztof
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2026-08-17 6:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-15 1:57 [PATCH 0/2] dt-bindings: Add Xuantie Semiconductor Co., Ltd Guo Ren
2026-08-15 1:57 ` [PATCH 1/2] dt-bindings: vendor-prefixes: Add Xuantie Semiconductor Guo Ren
2026-08-17 6:08 ` Krzysztof Kozlowski [this message]
2026-08-17 9:42 ` Guo Ren
2026-08-15 1:57 ` [PATCH 2/2] dt-bindings: riscv: Add Xuantie C906/C908/C910/C920 compatibles Guo Ren
2026-08-15 19:44 ` Shengyu Qu
2026-08-17 1:40 ` Guo Ren
2026-08-17 6:10 ` Krzysztof Kozlowski
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=bf81034d-7768-40f3-b078-e17ea3a2e665@kernel.org \
--to=krzk@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=guoren@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=robh+dt@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