From: Chester Lin <clin@suse.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "Chester Lin" <clin@suse.com>,
s32@nxp.com, linux-gpio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
"Ghennadi Procopciuc" <Ghennadi.Procopciuc@oss.nxp.com>,
"Andrei Stefanescu" <andrei.stefanescu@nxp.com>,
"Andreas Färber" <afaerber@suse.de>,
"Matthias Brugger" <mbrugger@suse.com>
Subject: [PATCH v4 3/3] MAINTAINERS: Add NXP S32 pinctrl maintainer and reviewer
Date: Wed, 18 Jan 2023 17:47:28 +0800 [thread overview]
Message-ID: <20230118094728.3814-4-clin@suse.com> (raw)
In-Reply-To: <20230118094728.3814-1-clin@suse.com>
Add myself as a maintainer and add NXP S32 Linux Team as a review group for
S32 pinctrl patches.
Signed-off-by: Chester Lin <clin@suse.com>
---
Changes in v4:
- The initial version in this series.
MAINTAINERS | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 42fc47c6edfd..9c9850194891 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -16551,6 +16551,14 @@ S: Supported
F: drivers/gpio/gpio-sama5d2-piobu.c
F: drivers/pinctrl/pinctrl-at91*
+PIN CONTROLLER - NXP S32
+M: Chester Lin <clin@suse.com>
+R: NXP S32 Linux Team <s32@nxp.com>
+L: linux-gpio@vger.kernel.org
+S: Maintained
+F: Documentation/devicetree/bindings/pinctrl/nxp,s32*
+F: drivers/pinctrl/nxp/
+
PIN CONTROLLER - QUALCOMM
M: Bjorn Andersson <andersson@kernel.org>
L: linux-arm-msm@vger.kernel.org
--
2.37.3
prev parent reply other threads:[~2023-01-18 10:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 9:47 [PATCH v4 0/3] Add pinctrl support for S32 SoC family Chester Lin
2023-01-18 9:47 ` [PATCH v4 1/3] dt-bindings: pinctrl: add schema for NXP S32 SoCs Chester Lin
2023-01-18 16:48 ` Rob Herring
2023-01-18 9:47 ` [PATCH v4 2/3] pinctrl: add NXP S32 SoC family support Chester Lin
2023-01-26 13:25 ` Linus Walleij
2023-02-01 15:31 ` Chester Lin
2023-01-18 9:47 ` Chester Lin [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=20230118094728.3814-4-clin@suse.com \
--to=clin@suse.com \
--cc=Ghennadi.Procopciuc@oss.nxp.com \
--cc=afaerber@suse.de \
--cc=andrei.stefanescu@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbrugger@suse.com \
--cc=s32@nxp.com \
/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
Powered by JetHome