From: Matthias Brugger <mbrugger@suse.com>
To: Chester Lin <clin@suse.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, soc@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org,
"Chester Lin" <chester62515@gmail.com>,
"NXP S32 Linux Team" <s32@nxp.com>,
"Arnd Bergmann" <arnd@arndb.de>,
"Olof Johansson" <olof@lixom.net>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [PATCH] MAINTAINERS: change the S32G2 maintainer's email address.
Date: Thu, 16 Nov 2023 15:37:01 +0100 [thread overview]
Message-ID: <fbce74d9-34ab-41a0-803b-c38c86baee89@suse.com> (raw)
In-Reply-To: <20231115234508.11510-1-clin@suse.com>
On 16/11/2023 00:45, Chester Lin wrote:
> I am leaving SUSE so the current email address <clin@suse.com> will be
> disabled soon. <chester62515@gmail.com> will be my new address for handling
> emails, patches and pull requests from upstream and communities.
>
> Cc: Chester Lin <chester62515@gmail.com>
> Cc: NXP S32 Linux Team <s32@nxp.com>
> Cc: Arnd Bergmann <arnd@arndb.de>
> Cc: Olof Johansson <olof@lixom.net>
> Cc: Andreas Färber <afaerber@suse.de>
> Cc: Matthias Brugger <mbrugger@suse.com>
> Signed-off-by: Chester Lin <clin@suse.com>
Reviewed-by: Matthias Brugger <mbrugger@suse.com>
You might think of updating .mailmap file as well.
Regards,
Matthias
> ---
> MAINTAINERS | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 5c9f868e13b6..84de6a1793c3 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -2535,7 +2535,7 @@ F: drivers/*/*/*wpcm*
> F: drivers/*/*wpcm*
>
> ARM/NXP S32G ARCHITECTURE
> -M: Chester Lin <clin@suse.com>
> +M: Chester Lin <chester62515@gmail.com>
> R: Andreas Färber <afaerber@suse.de>
> R: Matthias Brugger <mbrugger@suse.com>
> R: NXP S32 Linux Team <s32@nxp.com>
next prev parent reply other threads:[~2023-11-16 14:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-15 23:45 [PATCH] MAINTAINERS: change the S32G2 maintainer's email address Chester Lin
2023-11-16 14:37 ` Matthias Brugger [this message]
2023-12-06 16:40 ` patchwork-bot+linux-soc
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=fbce74d9-34ab-41a0-803b-c38c86baee89@suse.com \
--to=mbrugger@suse.com \
--cc=afaerber@suse.de \
--cc=arnd@arndb.de \
--cc=chester62515@gmail.com \
--cc=clin@suse.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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