Re: [PATCH 1/2] dt-bindings: vendor-prefixes: Add Xuantie Semiconductor
Guo Ren <[email protected]>
| Newsgroups | org.infradead.lists.linux-riscv,org.kernel.vger.linux-devicetree,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <CAJF2gTQGbQ7bUM-itiZhqaPM0-6oy_oV6FrNKfFTgvAV4_YW5A@mail.gmail.com> |
On Mon, Aug 17, 2026 at 2:08 PM Krzysztof Kozlowski <[email protected]> wrote: > > On 15/08/2026 03:57, Guo Ren wrote: > > From: "GUO Ren (XuanTie)" <[email protected]> > > > > 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 <[email protected]> > > Cc: devicetree <[email protected]> > > 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. Thanks for pointing that out; I would drop the autogenerated scripts/get_maintainer.pl CC entries. > > If you need it for your own patch management purposes, keep it under the > --- separator. > > > > Signed-off-by: GUO Ren (XuanTie) <[email protected]> > > --- > > 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. Okay, I'll try that. -- Best Regards Guo Ren _______________________________________________ linux-riscv mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-riscv