From: Peter Chen <peter.chen@cixtech.com>
To: soc@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, catalin.marinas@arm.com, will@kernel.org,
arnd@arndb.de
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, cix-kernel-upstream@cixtech.com,
marcin@juszkiewicz.com.pl, maz@kernel.org,
kajetan.puchalski@arm.com, Peter Chen <peter.chen@cixtech.com>,
Fugang Duan <fugang.duan@cixtech.com>
Subject: [PATCH v5 6/6] MAINTAINERS: Add CIX SoC maintainer entry
Date: Mon, 24 Mar 2025 14:24:20 +0800 [thread overview]
Message-ID: <20250324062420.360289-7-peter.chen@cixtech.com> (raw)
In-Reply-To: <20250324062420.360289-1-peter.chen@cixtech.com>
Using this entry as the maintainers information for CIX SoCs.
Acked-by: Fugang Duan <fugang.duan@cixtech.com>
Signed-off-by: Peter Chen <peter.chen@cixtech.com>
---
Changes for v5:
- Refine MAINTAINERS for all CIX SoC
- Add T for code tree location
- Add K for Content regex
Changes for v4:
- Add two dts files as maintained files
MAINTAINERS | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index efee40ea589f..f400e2de573b 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -2354,6 +2354,17 @@ F: arch/arm/boot/compressed/misc-ep93xx.h
F: arch/arm/mach-ep93xx/
F: drivers/iio/adc/ep93xx_adc.c
+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
+T: git git://git.kernel.org/pub/scm/linux/kernel/git/peter.chen/cix.git
+F: Documentation/devicetree/bindings/arm/cix.yaml
+F: arch/arm64/boot/dts/cix/
+K: \bcix\b
+
ARM/CLKDEV SUPPORT
M: Russell King <linux@armlinux.org.uk>
L: linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
--
2.25.1
prev parent reply other threads:[~2025-03-24 6:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-24 6:24 [PATCH v5 0/6] arm64: Introduce CIX P1 (SKY1) SoC Peter Chen
2025-03-24 6:24 ` [PATCH v5 1/6] dt-bindings: vendor-prefixes: Add CIX Technology Group Co., Ltd Peter Chen
2025-03-24 6:24 ` [PATCH v5 2/6] dt-bindings: arm: add CIX P1 (SKY1) SoC Peter Chen
2025-03-24 6:24 ` [PATCH v5 3/6] arm64: Kconfig: add ARCH_CIX for cix silicons Peter Chen
2025-03-24 6:24 ` [PATCH v5 4/6] arm64: defconfig: Enable CIX SoC Peter Chen
2025-03-24 6:24 ` [PATCH v5 5/6] arm64: dts: cix: add initial CIX P1(SKY1) dts support Peter Chen
2025-03-25 10:52 ` Marc Zyngier
2025-03-26 3:26 ` Peter Chen
2025-03-26 9:12 ` Marc Zyngier
2025-03-27 6:44 ` Peter Chen
2025-03-27 7:16 ` Krzysztof Kozlowski
2025-03-27 8:18 ` Arnd Bergmann
2025-03-27 9:31 ` Peter Chen
2025-03-27 10:29 ` Arnd Bergmann
2025-03-27 8:35 ` Peter Chen
2025-03-27 8:40 ` Krzysztof Kozlowski
2025-03-27 9:47 ` Peter Chen
2025-03-27 13:06 ` Krzysztof Kozlowski
2025-03-24 6:24 ` Peter Chen [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=20250324062420.360289-7-peter.chen@cixtech.com \
--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=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcin@juszkiewicz.com.pl \
--cc=maz@kernel.org \
--cc=robh@kernel.org \
--cc=soc@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;
as well as URLs for NNTP newsgroup(s).