From: Chester Lin <clin@suse.com>
To: "Rob Herring" <robh+dt@kernel.org>,
devicetree@vger.kernel.org, "Andreas Färber" <afaerber@suse.de>,
"Matthias Brugger" <mbrugger@suse.com>,
"Krzysztof Kozlowski" <krzk@kernel.org>
Cc: s32@nxp.com, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-serial@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Shawn Guo <shawnguo@kernel.org>, Li Yang <leoyang.li@nxp.com>,
catalin-dan.udma@nxp.com, bogdan.hamciuc@nxp.com,
bogdan.folea@nxp.com, ciprianmarian.costea@nxp.com,
Radu Nicolae Pirea <radu-nicolae.pirea@oss.nxp.com>,
ghennadi.procopciuc@nxp.com, "Ivan T . Ivanov" <iivanov@suse.de>,
"Lee, Chun-Yi" <jlee@suse.com>, Chester Lin <clin@suse.com>
Subject: [PATCH v2 8/8] MAINTAINERS: add an entry for NXP S32G boards
Date: Wed, 8 Sep 2021 14:45:28 +0800 [thread overview]
Message-ID: <20210908064528.922-9-clin@suse.com> (raw)
In-Reply-To: <20210908064528.922-1-clin@suse.com>
Add a new entry for the maintenance of NXP S32G DT files.
Signed-off-by: Chester Lin <clin@suse.com>
---
Changes in v2:
- Add information of reviewers.
MAINTAINERS | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 5a61cb2d0cd4..6f2a3f8ae88e 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -2308,6 +2308,14 @@ F: arch/arm/boot/dts/nuvoton-wpcm450*
F: arch/arm/mach-npcm/wpcm450.c
F: drivers/*/*wpcm*
+ARM/NXP S32G ARCHITECTURE
+M: Chester Lin <clin@suse.com>
+R: Andreas Färber <afaerber@suse.de>
+R: Matthias Brugger <mbrugger@suse.com>
+L: linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
+S: Maintained
+F: arch/arm64/boot/dts/freescale/s32g*.dts*
+
ARM/OPENMOKO NEO FREERUNNER (GTA02) MACHINE SUPPORT
L: openmoko-kernel@lists.openmoko.org (subscribers-only)
S: Orphan
--
2.30.0
next prev parent reply other threads:[~2021-09-08 6:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 6:45 [PATCH v2 0/8] arm64: dts: initial NXP S32G2 support Chester Lin
2021-09-08 6:45 ` [PATCH v2 1/8] dt-bindings: arm: fsl: add NXP S32G2 boards Chester Lin
2021-09-08 6:45 ` [PATCH v2 2/8] dt-bindings: serial: fsl-linflexuart: convert to json-schema format Chester Lin
2021-09-20 22:32 ` Rob Herring
2021-09-08 6:45 ` [PATCH v2 3/8] dt-bindings: serial: fsl-linflexuart: add compatible for S32G2 Chester Lin
2021-09-20 22:32 ` Rob Herring
2021-09-08 6:45 ` [PATCH v2 4/8] arm64: dts: add NXP S32G2 support Chester Lin
2021-09-08 6:45 ` [PATCH v2 5/8] arm64: dts: s32g2: add serial/uart support Chester Lin
2021-09-08 6:45 ` [PATCH v2 6/8] arm64: dts: s32g2: add VNP-EVB and VNP-RDB2 support Chester Lin
2021-09-08 6:45 ` [PATCH v2 7/8] arm64: dts: s32g2: add memory nodes for evb and rdb2 Chester Lin
2021-09-08 6:45 ` Chester Lin [this message]
2021-10-04 8:11 ` [PATCH v2 0/8] arm64: dts: initial NXP S32G2 support Shawn Guo
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=20210908064528.922-9-clin@suse.com \
--to=clin@suse.com \
--cc=afaerber@suse.de \
--cc=bogdan.folea@nxp.com \
--cc=bogdan.hamciuc@nxp.com \
--cc=catalin-dan.udma@nxp.com \
--cc=ciprianmarian.costea@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=ghennadi.procopciuc@nxp.com \
--cc=gregkh@linuxfoundation.org \
--cc=iivanov@suse.de \
--cc=jlee@suse.com \
--cc=krzk@kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mbrugger@suse.com \
--cc=radu-nicolae.pirea@oss.nxp.com \
--cc=robh+dt@kernel.org \
--cc=s32@nxp.com \
--cc=shawnguo@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).