linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Masami Hiramatsu <mhiramat@kernel.org>
To: Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: naveen.n.rao@linux.ibm.com, anil.s.keshavamurthy@intel.com,
	davem@davemloft.net, rostedt@goodmis.org, mingo@redhat.com,
	corbet@lwn.net, akpm@linux-foundation.org,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 4/4] MAINTAINERS: Update KPROBES and TRACING entries
Date: Tue, 26 Oct 2021 17:28:42 +0900	[thread overview]
Message-ID: <20211026172842.cb6fc83f888ade50d0b6046c@kernel.org> (raw)
In-Reply-To: <1635213091-24387-5-git-send-email-yangtiezhu@loongson.cn>

On Tue, 26 Oct 2021 09:51:31 +0800
Tiezhu Yang <yangtiezhu@loongson.cn> wrote:

> There is no git tree for KPROBES in MAINTAINERS, it is not convinent to
> rebase, lib/test_kprobes.c and samples/kprobes belong to kprobe, so add
> git tree and missing files for KPROBES, and also use linux-trace.git for
> TRACING to avoid confusing.
> 
> Signed-off-by: Tiezhu Yang <yangtiezhu@loongson.cn>

This looks good to me for kprobe section.

Acked-by: Masami Hiramatsu <mhiramat@kernel.org>

Thank you,

> ---
>  MAINTAINERS | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 5b33791..8d26693 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -10437,10 +10437,13 @@ M:	Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>
>  M:	"David S. Miller" <davem@davemloft.net>
>  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/kprobes.rst
>  F:	include/asm-generic/kprobes.h
>  F:	include/linux/kprobes.h
>  F:	kernel/kprobes.c
> +F:	lib/test_kprobes.c
> +F:	samples/kprobes
>  
>  KS0108 LCD CONTROLLER DRIVER
>  M:	Miguel Ojeda <ojeda@kernel.org>
> @@ -18967,7 +18970,7 @@ TRACING
>  M:	Steven Rostedt <rostedt@goodmis.org>
>  M:	Ingo Molnar <mingo@redhat.com>
>  S:	Maintained
> -T:	git git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git perf/core
> +T:	git git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
>  F:	Documentation/trace/ftrace.rst
>  F:	arch/*/*/*/ftrace.h
>  F:	arch/*/kernel/ftrace.c
> -- 
> 2.1.0
> 


-- 
Masami Hiramatsu <mhiramat@kernel.org>

  reply	other threads:[~2021-10-26  8:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-26  1:51 [PATCH v2 0/4] Do some changes about kprobe and trace Tiezhu Yang
2021-10-26  1:51 ` [PATCH v2 1/4] samples/kretprobes: Fix return value if register_kretprobe() failed Tiezhu Yang
2021-10-26  1:51 ` [PATCH v2 2/4] docs, kprobes: Remove invalid URL and add new reference Tiezhu Yang
2021-10-26  1:51 ` [PATCH v2 3/4] test_kprobes: Move it from kernel/ to lib/ Tiezhu Yang
2021-10-26  1:51 ` [PATCH v2 4/4] MAINTAINERS: Update KPROBES and TRACING entries Tiezhu Yang
2021-10-26  8:28   ` Masami Hiramatsu [this message]
2021-10-26 13:04     ` Steven Rostedt

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=20211026172842.cb6fc83f888ade50d0b6046c@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=anil.s.keshavamurthy@intel.com \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=naveen.n.rao@linux.ibm.com \
    --cc=rostedt@goodmis.org \
    --cc=yangtiezhu@loongson.cn \
    /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).