From: Wei Li <liwei391@huawei.com>
To: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>
Cc: <linux-perf-users@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <rui.xiang@huawei.com>
Subject: [PATCH 0/2] perf tools: Fix mis-matching of perf sub-commands
Date: Fri, 31 Dec 2021 14:30:42 +0800 [thread overview]
Message-ID: <20211231063044.2405691-1-liwei391@huawei.com> (raw)
We support short command 'rec*' for 'record' and 'rep*' for 'report' in
lots of sub-commands, but the matching is not quite strict currnetly.
It may be puzzling sometime, like we mis-type a 'recport' to report but
it will perform 'record' in fact without any message. So fix the
mis-matching.
Wei Li (2):
perf string: Add strcmp_prefix()
perf tools: Enhance the matching of sub-commands
tools/perf/builtin-c2c.c | 5 +++--
tools/perf/builtin-kmem.c | 2 +-
tools/perf/builtin-kvm.c | 9 +++++----
tools/perf/builtin-lock.c | 5 +++--
tools/perf/builtin-mem.c | 5 +++--
tools/perf/builtin-sched.c | 4 ++--
tools/perf/builtin-script.c | 6 ++++--
tools/perf/builtin-stat.c | 4 ++--
tools/perf/builtin-timechart.c | 3 ++-
tools/perf/util/string.c | 17 +++++++++++++++++
tools/perf/util/string2.h | 1 +
11 files changed, 43 insertions(+), 18 deletions(-)
--
2.25.1
next reply other threads:[~2021-12-31 6:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-31 6:30 Wei Li [this message]
2021-12-31 6:30 ` [PATCH 1/2] perf string: Add strcmp_prefix() Wei Li
2021-12-31 6:30 ` [PATCH 2/2] perf tools: Enhance the matching of sub-commands Wei Li
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=20211231063044.2405691-1-liwei391@huawei.com \
--to=liwei391@huawei.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=rui.xiang@huawei.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).