From: Steven Rostedt <rostedt@goodmis.org>
To: Zhang Chujun <zhangchujun@cmss.chinamobile.com>
Cc: linux-trace-devel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tracing: fix incorrcet short option in usage text for --threads
Date: Thu, 6 Nov 2025 20:00:41 -0500 [thread overview]
Message-ID: <20251106200041.6f21af65@batman.local.home> (raw)
In-Reply-To: <20251106031040.1869-1-zhangchujun@cmss.chinamobile.com>
On Thu, 6 Nov 2025 11:10:40 +0800
Zhang Chujun <zhangchujun@cmss.chinamobile.com> wrote:
> The help message incorrectly listed '-t' as the short option for
> --threads, but the actual getopt_long configuration uses '-e'.
> This mismatch can confuse users and lead to incorrect command-line
> usage. This patch updates the usage string to correctly show:
> "-e, --threads NRTHR"
> to match the implementation.
>
> Note: checkpatch.pl reports a false-positive spelling warning on
> 'Run', which is intentional.
I'll pull this manually, but you sent to the wrong mailing list. It
should go to linux-trace-kernel@vger.kernel.org and not
linux-trace-devel. That's for user space tools that do not live in the
kernel proper.
-- Steve
>
> Signed-off-by: Zhang Chujun <zhangchujun@cmss.chinamobile.com>
>
> diff --git a/tools/tracing/latency/latency-collector.c b/tools/tracing/latency/latency-collector.c
> index cf263fe9deaf..ef97916e3873 100644
> --- a/tools/tracing/latency/latency-collector.c
> +++ b/tools/tracing/latency/latency-collector.c
> @@ -1725,7 +1725,7 @@ static void show_usage(void)
> "-n, --notrace\t\tIf latency is detected, do not print out the content of\n"
> "\t\t\tthe trace file to standard output\n\n"
>
> -"-t, --threads NRTHR\tRun NRTHR threads for printing. Default is %d.\n\n"
> +"-e, --threads NRTHR\tRun NRTHR threads for printing. Default is %d.\n\n"
>
> "-r, --random\t\tArbitrarily sleep a certain amount of time, default\n"
> "\t\t\t%ld ms, before reading the trace file. The\n"
prev parent reply other threads:[~2025-11-07 1:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 3:10 [PATCH] tracing: fix incorrcet short option in usage text for --threads Zhang Chujun
2025-11-07 1:00 ` Steven Rostedt [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=20251106200041.6f21af65@batman.local.home \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=zhangchujun@cmss.chinamobile.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;
as well as URLs for NNTP newsgroup(s).