public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eiichi Tsukata <devel@etsukata.com>
To: rostedt@goodmis.org, mingo@redhat.com, srikar@linux.vnet.ibm.com,
	mhiramat@kernel.org, linux-kernel@vger.kernel.org
Cc: Eiichi Tsukata <devel@etsukata.com>
Subject: [PATCH 2/2] tracing/uprobe: Fix obsolete comment on trace_uprobe_create()
Date: Fri, 14 Jun 2019 16:40:26 +0900	[thread overview]
Message-ID: <20190614074026.8045-2-devel@etsukata.com> (raw)
In-Reply-To: <20190614074026.8045-1-devel@etsukata.com>

Commit 0597c49c69d5 ("tracing/uprobes: Use dyn_event framework for
uprobe events") cleaned up the usage of trace_uprobe_create(), and the
function has been no longer used for removing uprobe/uretprobe.

Signed-off-by: Eiichi Tsukata <devel@etsukata.com>
---
 kernel/trace/trace_uprobe.c | 2 --
 1 file changed, 2 deletions(-)

diff --git a/kernel/trace/trace_uprobe.c b/kernel/trace/trace_uprobe.c
index 7dc8ee55cf84..7860e3f59fad 100644
--- a/kernel/trace/trace_uprobe.c
+++ b/kernel/trace/trace_uprobe.c
@@ -426,8 +426,6 @@ static int register_trace_uprobe(struct trace_uprobe *tu)
 /*
  * Argument syntax:
  *  - Add uprobe: p|r[:[GRP/]EVENT] PATH:OFFSET [FETCHARGS]
- *
- *  - Remove uprobe: -:[GRP/]EVENT
  */
 static int trace_uprobe_create(int argc, const char **argv)
 {
-- 
2.21.0


  reply	other threads:[~2019-06-14  7:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-14  7:40 [PATCH 1/2] tracing/uprobe: Fix NULL pointer dereference in trace_uprobe_create() Eiichi Tsukata
2019-06-14  7:40 ` Eiichi Tsukata [this message]
2019-06-14 12:32   ` [PATCH 2/2] tracing/uprobe: Fix obsolete comment on trace_uprobe_create() Srikar Dronamraju
2019-06-14 12:29 ` [PATCH 1/2] tracing/uprobe: Fix NULL pointer dereference in trace_uprobe_create() Srikar Dronamraju
2019-06-21 14:22 ` 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=20190614074026.8045-2-devel@etsukata.com \
    --to=devel@etsukata.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=srikar@linux.vnet.ibm.com \
    /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