From: Ghennadi Procopciuc <ghennadi.procopciuc@oss.nxp.com>
To: "Arnd Bergmann" <arnd@arndb.de>,
"Olof Johansson" <olof@lixom.net>,
"Chester Lin" <chester62515@gmail.com>,
krzysztof.kozlowski+dt@linaro.org,
"Andreas Färber" <afaerber@suse.de>,
"Matthias Brugger" <mbrugger@suse.com>,
robh+dt@kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, soc@kernel.org,
NXP S32 Linux Team <s32@nxp.com>,
Ghennadi Procopciuc <ghennadi.procopciuc@oss.nxp.com>
Subject: [PATCH 0/1] MAINTAINERS: Add S32G SoC maintainer
Date: Wed, 21 Feb 2024 14:01:21 +0200 [thread overview]
Message-ID: <20240221120123.1118552-1-ghennadi.procopciuc@oss.nxp.com> (raw)
Add myself as co-maintainer for the S32G platform alongside Chester Lin, as I am
directly involved in developing and maintaining the downstream version of the
kernel and Linux BSP for this platform.
Ghennadi Procopciuc (1):
MAINTAINERS: Add maintainer for NXP S32G boards
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
--
2.43.2
next reply other threads:[~2024-02-21 12:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 12:01 Ghennadi Procopciuc [this message]
2024-02-21 12:01 ` [PATCH 1/1] MAINTAINERS: Add maintainer for NXP S32G boards Ghennadi Procopciuc
2024-02-21 14:42 ` Krzysztof Kozlowski
2024-02-21 14:45 ` Krzysztof Kozlowski
2024-02-21 15:19 ` Ghennadi Procopciuc
2024-02-21 15:43 ` Krzysztof Kozlowski
2024-02-21 17:00 ` Ghennadi Procopciuc
2024-02-22 11:13 ` Krzysztof Kozlowski
2024-02-23 12:02 ` Matthias Brugger
2024-02-23 12:29 ` Arnd Bergmann
2024-02-23 14:42 ` Shawn Guo
2024-02-24 7:25 ` Chester Lin
2024-02-24 7:56 ` Chester Lin
2024-02-24 11:42 ` Arnd Bergmann
2024-02-26 7:33 ` Ghennadi Procopciuc
2024-02-26 9:55 ` Matthias Brugger
2024-02-28 15:19 ` Matthias Brugger
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=20240221120123.1118552-1-ghennadi.procopciuc@oss.nxp.com \
--to=ghennadi.procopciuc@oss.nxp.com \
--cc=afaerber@suse.de \
--cc=arnd@arndb.de \
--cc=chester62515@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbrugger@suse.com \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=s32@nxp.com \
--cc=soc@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 read-only IMAP folder(s) and NNTP newsgroup(s).