From: Peter Chen <peter.chen@cixtech.com>
To: Kajetan Puchalski <kajetan.puchalski@arm.com>,
Krzysztof Kozlowski <krzk@kernel.org>
Cc: <robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<catalin.marinas@arm.com>, <will@kernel.org>, <arnd@arndb.de>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<cix-kernel-upstream@cixtech.com>, <marcin@juszkiewicz.com.pl>,
Fugang Duan <fugang.duan@cixtech.com>
Subject: Re: [PATCH v4 6/6] MAINTAINERS: Add CIX SoC maintainer entry
Date: Fri, 21 Mar 2025 09:40:00 +0800 [thread overview]
Message-ID: <Z9zDcMRVqAcJW8H7@nchen-desktop> (raw)
In-Reply-To: <zsmeh4ukuspyetowryqi3blcquxlua5wzy5ibgy7lupryr5txx@74ic6drtremv>
On 25-03-20 15:28:49, Kajetan Puchalski wrote:
>
> > > > +ARM/CIX SKY ARM ARCHITECTURE
> > > > +M: Peter Chen <peter.chen@cixtech.com>
> > > > +M: Fugang Duan <fugang.duan@cixtech.com>
> > > > +R: CIX Linux Kernel Upstream Group <cix-kernel-upstream@cixtech.com>
> > > > +L: linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
> > > > +S: Maintained
> > > > +F: Documentation/devicetree/bindings/arm/cix.yaml
> > > > +F: arch/arm64/boot/dts/cix/sky1-orion-o6.dts
> > > > +F: arch/arm64/boot/dts/cix/sky1.dtsi
> > >
> > > Instead:
> > > arch/arm64/boot/dts/cix/
> > >
> > > or if you think there will be more different architectures coming from
> > > cix, which you will not maintain, then useful would be a "sky" subdirectory.
> > >
> > Hi Krzysztof,
> >
> > Thanks for your comment, CIX is Arm SoC based silicon design
> > company, we may have different SoC style for middle end in future.
> > So, for that SoC series, it may not name sky.
>
> I believe the idea is that the file should either say
>
> +F: arch/arm64/boot/dts/cix/
>
> if the two of you intend to be maintainers for everything under cix/.
> You don't need to list every specific file.
>
> Otherwise it should say
>
> +F: arch/arm64/boot/dts/cix/sky/
>
> with its own subdirectory if you only intend to be maintaining the sky family.
Hi Kajetan & Krzysztof,
Thanks for your valuable comments. We prefer maintain the entire
CIX architecture under one entry, I will change maintain information
like below:
ARM/CIX SOC SUPPORT
M: Peter Chen <peter.chen@cixtech.com>
M: Fugang Duan <fugang.duan@cixtech.com>
R: CIX Linux Kernel Upstream Group <cix-kernel-upstream@cixtech.com>
L: linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
S: Maintained
F: Documentation/devicetree/bindings/arm/cix.yaml
F: arch/arm64/boot/dts/cix/
--
Best regards,
Peter
next prev parent reply other threads:[~2025-03-21 1:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 5:38 [PATCH v4 0/6] arm64: Introduce CIX P1 (SKY1) SoC Peter Chen
2025-03-05 5:38 ` [PATCH v4 1/6] dt-bindings: vendor-prefixes: Add CIX Technology Group Co., Ltd Peter Chen
2025-03-05 5:38 ` [PATCH v4 2/6] dt-bindings: arm: add CIX P1 (SKY1) SoC Peter Chen
2025-03-05 5:38 ` [PATCH v4 3/6] arm64: Kconfig: add ARCH_CIX for cix silicons Peter Chen
2025-03-05 5:38 ` [PATCH v4 4/6] arm64: defconfig: Enable CIX SoC Peter Chen
2025-03-05 5:38 ` [PATCH v4 5/6] arm64: dts: cix: add initial CIX P1(SKY1) dts support Peter Chen
2025-03-20 9:36 ` Marc Zyngier
2025-03-20 9:57 ` Peter Chen
2025-03-21 9:04 ` Marc Zyngier
2025-03-21 10:31 ` Peter Chen
2025-03-21 11:01 ` Marc Zyngier
2025-03-05 5:38 ` [PATCH v4 6/6] MAINTAINERS: Add CIX SoC maintainer entry Peter Chen
2025-03-20 9:25 ` Krzysztof Kozlowski
2025-03-20 10:49 ` Peter Chen
2025-03-20 15:28 ` Kajetan Puchalski
2025-03-21 1:40 ` Peter Chen [this message]
2025-03-20 16:20 ` Krzysztof Kozlowski
2025-03-21 9:00 ` Arnd Bergmann
2025-03-11 1:02 ` [PATCH v4 0/6] arm64: Introduce CIX P1 (SKY1) SoC Peter Chen
2025-03-17 1:38 ` Peter Chen
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=Z9zDcMRVqAcJW8H7@nchen-desktop \
--to=peter.chen@cixtech.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=cix-kernel-upstream@cixtech.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fugang.duan@cixtech.com \
--cc=kajetan.puchalski@arm.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcin@juszkiewicz.com.pl \
--cc=robh@kernel.org \
--cc=will@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