All of lore.kernel.org
 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, corbet@lwn.net, ananth@in.ibm.com,
	akpm@linux-foundation.org, randy.dunlap@oracle.com,
	mathieu.desnoyers@polymtl.ca, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH 4/4] MAINTAINERS: Add git tree and missing files for KPROBES
Date: Mon, 25 Oct 2021 15:38:21 +0900	[thread overview]
Message-ID: <20211025153821.baa3f5d90fd40943ee28d2e1@kernel.org> (raw)
In-Reply-To: <1635132660-5038-5-git-send-email-yangtiezhu@loongson.cn>

On Mon, 25 Oct 2021 11:31:00 +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, add them.
> 
> Signed-off-by: Tiezhu Yang <yangtiezhu@loongson.cn>
> ---
>  MAINTAINERS | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 4372473..0e9bc60 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -10506,10 +10506,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/mhiramat/linux.git

NACK. As I said, this branch was prepared when I discussed with tip maintainer 
on kretprobe stackfix series but now it has been maintained on Steve's tracing
tree.

Steve, should we put your tree here?

Anyway, I will pick your [1/4]-[3/4].

Thank you,

>  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>
> -- 
> 2.1.0
> 


-- 
Masami Hiramatsu <mhiramat@kernel.org>

  reply	other threads:[~2021-10-25  6:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-25  3:30 [PATCH 0/4] Do some changes about kprobe Tiezhu Yang
2021-10-25  3:30 ` [PATCH 1/4] samples/kretprobes: Fix return value if register_kretprobe() failed Tiezhu Yang
2021-10-25  6:15   ` Masami Hiramatsu
2021-10-25  3:30 ` [PATCH 2/4] docs, kprobes: Remove invalid URL and add new reference Tiezhu Yang
2021-10-25  6:29   ` Masami Hiramatsu
2021-10-25  3:30 ` [PATCH 3/4] test_kprobes: Move it from kernel/ to lib/ Tiezhu Yang
2021-10-25  6:33   ` Masami Hiramatsu
2021-10-25  3:31 ` [PATCH 4/4] MAINTAINERS: Add git tree and missing files for KPROBES Tiezhu Yang
2021-10-25  6:38   ` Masami Hiramatsu [this message]
2021-10-25  8:31     ` Tiezhu Yang
2021-10-25 14:48       ` Steven Rostedt
2021-10-25  6:14 ` [PATCH 0/4] Do some changes about kprobe 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=20211025153821.baa3f5d90fd40943ee28d2e1@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=ananth@in.ibm.com \
    --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=mathieu.desnoyers@polymtl.ca \
    --cc=naveen.n.rao@linux.ibm.com \
    --cc=randy.dunlap@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.