From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: kan.liang@linux.intel.com
Cc: peterz@infradead.org, mingo@redhat.com, namhyung@kernel.org,
irogers@google.com, adrian.hunter@intel.com, jolsa@kernel.org,
alexander.shishkin@linux.intel.com, mark.rutland@arm.com,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
dave.hansen@linux.intel.com
Subject: Re: [PATCH] MAINTAINERS: Remove myself from perf_events subsystem
Date: Wed, 1 Oct 2025 11:12:23 -0300 [thread overview]
Message-ID: <aN02x4MxhK3YjI35@x1> (raw)
In-Reply-To: <20250925162428.3516894-1-kan.liang@linux.intel.com>
On Thu, Sep 25, 2025 at 09:24:28AM -0700, kan.liang@linux.intel.com wrote:
> From: Kan Liang <kan.liang@linux.intel.com>
>
> I'm stepping down as the Reviewer of perf_events subsystem.
> It has been an honor and a pleasure to work with everyone to improve the
> perf_events subsystem. However, due to personal reasons, I have to leave
> Intel. I believe it would be difficult for me to continue in this role
> any further.
>
> Signed-off-by: Kan Liang <kan.liang@linux.intel.com>
I'm sorry to see you go, best wishes for your next endeavour!
Thanks, applied to perf-tools-next,
- Arnaldo
> ---
> MAINTAINERS | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index fe168477caa4..2c788294cf84 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -19759,7 +19759,6 @@ R: Alexander Shishkin <alexander.shishkin@linux.intel.com>
> R: Jiri Olsa <jolsa@kernel.org>
> R: Ian Rogers <irogers@google.com>
> R: Adrian Hunter <adrian.hunter@intel.com>
> -R: "Liang, Kan" <kan.liang@linux.intel.com>
> L: linux-perf-users@vger.kernel.org
> L: linux-kernel@vger.kernel.org
> S: Supported
> --
> 2.38.1
next prev parent reply other threads:[~2025-10-01 14:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-25 16:24 [PATCH] MAINTAINERS: Remove myself from perf_events subsystem kan.liang
2025-10-01 14:12 ` Arnaldo Carvalho de Melo [this message]
2025-10-03 4:38 ` Namhyung Kim
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=aN02x4MxhK3YjI35@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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