public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joel Fernandes <joel@joelfernandes.org>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Ingo Molnar <mingo@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Trace Devel <linux-trace-devel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH] tracing: Add Masami Hiramatsu as co-maintainer
Date: Mon, 3 Oct 2022 20:42:28 +0000	[thread overview]
Message-ID: <YztJNGLZvKKfYGjk@google.com> (raw)
In-Reply-To: <20221001091706.8efaeb64266efa6058a468df@kernel.org>

On Sat, Oct 01, 2022 at 09:17:06AM +0900, Masami Hiramatsu wrote:
> On Fri, 30 Sep 2022 12:41:31 -0400
> Steven Rostedt <rostedt@goodmis.org> wrote:
> 
> > From: "Steven Rostedt (Google)" <rostedt@goodmis.org>
> > 
> > Masami has been maintaining kprobes for a while now and that code has
> > been an integral part of tracing. He has also been an excellent reviewer
> > of all the tracing code and contributor as well.
> > 
> > The tracing subsystem needs another active maintainer to keep it running
> > smoothly, and I do not know anyone more qualified for the job than Masami.
> > 
> > Ingo has also told me that he has not been active in the tracing code for
> > some time and said he could be removed from the TRACING portion of the
> > MAINTAINERS file.
> > 
> > Acked-by: Ingo Molnar <mingo@kernel.org>
> > Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
> 
> Thanks Steve,
> 
> Acked-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
> 

Acked-by: Joel Fernandes (Google) <joel@joelfernandes.org>

thanks,

 - Joel


> > ---
> >  MAINTAINERS | 4 ++--
> >  1 file changed, 2 insertions(+), 2 deletions(-)
> > 
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index f5ca4aefd184..6c7c9cdff05a 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -20614,7 +20614,7 @@ F:	drivers/char/tpm/
> >  
> >  TRACING
> >  M:	Steven Rostedt <rostedt@goodmis.org>
> > -M:	Ingo Molnar <mingo@redhat.com>
> > +M:	Masami Hiramatsu <mhiramat@kernel.org>
> >  S:	Maintained
> >  T:	git git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
> >  F:	Documentation/trace/ftrace.rst
> > @@ -20630,7 +20630,7 @@ F:	tools/testing/selftests/ftrace/
> >  
> >  TRACING MMIO ACCESSES (MMIOTRACE)
> >  M:	Steven Rostedt <rostedt@goodmis.org>
> > -M:	Ingo Molnar <mingo@kernel.org>
> > +M:	Masami Hiramatsu <mhiramat@kernel.org>
> >  R:	Karol Herbst <karolherbst@gmail.com>
> >  R:	Pekka Paalanen <ppaalanen@gmail.com>
> >  L:	linux-kernel@vger.kernel.org
> > -- 
> > 2.35.1
> > 
> 
> 
> -- 
> Masami Hiramatsu (Google) <mhiramat@kernel.org>

      reply	other threads:[~2022-10-03 20:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-30 16:41 [PATCH] tracing: Add Masami Hiramatsu as co-maintainer Steven Rostedt
2022-10-01  0:17 ` Masami Hiramatsu
2022-10-03 20:42   ` Joel Fernandes [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=YztJNGLZvKKfYGjk@google.com \
    --to=joel@joelfernandes.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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