linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dongliang Mu <mudongliangabcd@gmail.com>
To: linux-trace-devel@vger.kernel.org
Cc: Dongliang Mu <mudongliangabcd@gmail.com>
Subject: [PATCH] Fix the description of check-events
Date: Fri,  7 Jun 2019 11:36:58 -0700	[thread overview]
Message-ID: <20190607183658.5605-1-mudongliangabcd@gmail.com> (raw)

Signed-off-by: Dongliang Mu <mudongliangabcd@gmail.com>
---
 tracecmd/trace-usage.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tracecmd/trace-usage.c b/tracecmd/trace-usage.c
index d2a1089..8db4241 100644
--- a/tracecmd/trace-usage.c
+++ b/tracecmd/trace-usage.c
@@ -283,7 +283,7 @@ static struct usage_help usage_help[] = {
 	{
 		"check-events",
 		"parse trace event formats",
-		" %s check-format [-N]\n"
+		" %s check-events [-N]\n"
 		"          -N do not load any plugins\n"
 	},
 	{
-- 
2.11.0


                 reply	other threads:[~2019-06-07 18:37 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20190607183658.5605-1-mudongliangabcd@gmail.com \
    --to=mudongliangabcd@gmail.com \
    --cc=linux-trace-devel@vger.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).