From: Suzuki K Poulose <suzuki.poulose@arm.com>
To: Mike Leach <mike.leach@linaro.org>,
linux-kernel@vger.kernel.org, coresight@lists.linaro.org
Subject: Re: [PATCH] MAINTAINERS: Change of email address
Date: Mon, 5 Jan 2026 11:20:38 +0000 [thread overview]
Message-ID: <693887e2-8de3-440c-804c-3bd1c588c060@arm.com> (raw)
In-Reply-To: <20251231171952.2307-1-mike.leach@linaro.org>
Hi Mike
On 31/12/2025 17:19, Mike Leach via CoreSight wrote:
> My e-mail address for linux work is changing to mike.leach@arm.com
> from 1st Jan 2026. Update MAINTAINERS file accordingly
>
> Signed-off-by: Mike Leach <mike.leach@linaro.org>
Please could you also sign-off by your arm email address ?
Also, it may be a good idea to add an entry to the .mailmap file.
Suzuki
> ---
> MAINTAINERS | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 5b11839cba9d..e3974f9f300a 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -2657,7 +2657,7 @@ N: digicolor
>
> ARM/CORESIGHT FRAMEWORK AND DRIVERS
> M: Suzuki K Poulose <suzuki.poulose@arm.com>
> -R: Mike Leach <mike.leach@linaro.org>
> +R: Mike Leach <mike.leach@arm.com>
> R: James Clark <james.clark@linaro.org>
> L: coresight@lists.linaro.org (moderated for non-subscribers)
> L: linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
> @@ -20476,7 +20476,7 @@ PERFORMANCE EVENTS TOOLING ARM64
> R: John Garry <john.g.garry@oracle.com>
> R: Will Deacon <will@kernel.org>
> R: James Clark <james.clark@linaro.org>
> -R: Mike Leach <mike.leach@linaro.org>
> +R: Mike Leach <mike.leach@arm.com>
> R: Leo Yan <leo.yan@linux.dev>
> L: linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
> S: Supported
prev parent reply other threads:[~2026-01-05 11:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-31 17:19 Mike Leach
2026-01-05 11:20 ` Suzuki K Poulose [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=693887e2-8de3-440c-804c-3bd1c588c060@arm.com \
--to=suzuki.poulose@arm.com \
--cc=coresight@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.leach@linaro.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
all inboxes | Powered by JetHome®