From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Dave Hansen <dave.hansen@linux.intel.com>
Cc: linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
linux-trace-kernel@vger.kernel.org,
Masami Hiramatsu <mhiramat@kernel.org>,
Naveen N Rao <naveen@kernel.org>
Subject: Re: [PATCH] MAINTAINERS: Remove bouncing kprobes maintainer
Date: Mon, 11 Aug 2025 15:53:52 +0900 [thread overview]
Message-ID: <20250811155352.45ee7061226f3e85aeda54b7@kernel.org> (raw)
In-Reply-To: <20250808180124.7DDE2ECD@davehans-spike.ostc.intel.com>
On Fri, 08 Aug 2025 11:01:24 -0700
Dave Hansen <dave.hansen@linux.intel.com> wrote:
>
> From: Dave Hansen <dave.hansen@linux.intel.com>
>
> The kprobes MAINTAINERS entry includes anil.s.keshavamurthy@intel.com.
> That address is bouncing. Remove it.
>
> This still leaves three other listed maintainers.
OK, should this be an urgent commit?
Thanks,
>
> Signed-off-by: Dave Hansen <dave.hansen@linux.intel.com>
> Cc: Naveen N Rao <naveen@kernel.org>
> Cc: "David S. Miller" <davem@davemloft.net>
> Cc: Masami Hiramatsu <mhiramat@kernel.org>
> Cc: linux-trace-kernel@vger.kernel.org
> ---
>
> b/MAINTAINERS | 1 -
> 1 file changed, 1 deletion(-)
>
> diff -puN MAINTAINERS~MAINTAINERS-kprobes MAINTAINERS
> --- a/MAINTAINERS~MAINTAINERS-kprobes 2025-08-08 10:57:53.686216444 -0700
> +++ b/MAINTAINERS 2025-08-08 10:58:00.237773836 -0700
> @@ -13681,7 +13681,6 @@ F: scripts/Makefile.kmsan
>
> KPROBES
> M: Naveen N Rao <naveen@kernel.org>
> -M: Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>
> M: "David S. Miller" <davem@davemloft.net>
> M: Masami Hiramatsu <mhiramat@kernel.org>
> L: linux-kernel@vger.kernel.org
> _
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next prev parent reply other threads:[~2025-08-11 6:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-08 18:01 [PATCH] MAINTAINERS: Remove bouncing kprobes maintainer Dave Hansen
2025-08-11 6:53 ` Masami Hiramatsu [this message]
2025-08-11 13:49 ` Dave Hansen
2025-08-14 2:45 ` Masami Hiramatsu
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=20250811155352.45ee7061226f3e85aeda54b7@kernel.org \
--to=mhiramat@kernel.org \
--cc=dave.hansen@linux.intel.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=naveen@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 NNTP newsgroup(s).