Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752649AbbB0KsQ (ORCPT ); Fri, 27 Feb 2015 05:48:16 -0500 Received: from szxga03-in.huawei.com ([119.145.14.66]:3365 "EHLO szxga03-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751539AbbB0KsP (ORCPT ); Fri, 27 Feb 2015 05:48:15 -0500 Message-ID: <54F04B42.1@huawei.com> Date: Fri, 27 Feb 2015 18:47:30 +0800 From: Yunlong Song User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Ingo Molnar CC: , , , , , Subject: Re: [PATCH] perf record: Remove the '--(null)' long_name for --list-opts References: <1424087904-3246-1-git-send-email-yunlong.song@huawei.com> <20150218175610.GA31995@gmail.com> In-Reply-To: <20150218175610.GA31995@gmail.com> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.111.74.205] X-CFilter-Loop: Reflected X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020205.54F04B68.0022,ss=1,re=0.001,recu=0.000,reip=0.000,cl=1,cld=1,fgs=0, ip=0.0.0.0, so=2013-05-26 15:14:31, dmn=2013-03-21 17:37:32 X-Mirapoint-Loop-Id: f91b24a1863513cc27d3e5b0b88d89a2 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3038 Lines: 88 On 2015/2/19 1:56, Ingo Molnar wrote: > > * Yunlong Song wrote: > >> If the long_name of a 'struct option' is defined as NULL, --list-opts >> will incorrectly print '--(null)' in its output. As a result, '--(null)' >> will finally appear in the case of bash completion, e.g. 'perf record --'. >> >> Example: >> >> Before this patch: >> >> $ perf record --list-opts >> >> --event --filter --pid --tid --realtime --no-buffering --raw-samples >> --all-cpus --cpu --count --output --no-inherit --freq --mmap-pages >> --group --(null) --call-graph --verbose --quiet --stat --data >> --timestamp --period --no-samples --no-buildid-cache --no-buildid >> --cgroup --delay --uid --branch-any --branch-filter --weight >> --transaction --per-thread --intr-regs >> >> After this patch: >> >> $ perf record --list-opts >> >> --event --filter --pid --tid --realtime --no-buffering --raw-samples >> --all-cpus --cpu --count --output --no-inherit --freq --mmap-pages >> --group --call-graph --verbose --quiet --stat --data --timestamp >> --period --no-samples --no-buildid-cache --no-buildid --cgroup --delay >> --uid --branch-any --branch-filter --weight --transaction --per-thread >> --intr-regs >> >> Signed-off-by: Yunlong Song >> --- >> tools/perf/util/parse-options.c | 3 ++- >> 1 file changed, 2 insertions(+), 1 deletion(-) >> >> diff --git a/tools/perf/util/parse-options.c b/tools/perf/util/parse-options.c >> index 4ee9a86..2bfe0b3 100644 >> --- a/tools/perf/util/parse-options.c >> +++ b/tools/perf/util/parse-options.c >> @@ -505,7 +505,8 @@ int parse_options_subcommand(int argc, const char **argv, const struct option *o >> break; >> case PARSE_OPT_LIST_OPTS: >> while (options->type != OPTION_END) { >> - printf("--%s ", options->long_name); >> + if (options->long_name) >> + printf("--%s ", options->long_name); > > There seems to be another 'perf record --list-opts' bug as > well: > > comet:~/tip> perf record --list-opts > --event --filter --pid --tid --realtime --no-buffering > --raw-samples --all-cpus --cpu --count --output > --no-inherit --freq --mmap-pages --group --(null) > --call-graph --verbose --quiet --stat --data --timestamp > --period --no-samples --no-buildid-cache --no-buildid > --cgroup --delay --uid --branch-any --branch-filter > --weight --transaction --per-thread --intr-regs comet:~/tip> > > Note the lack of newline at the end of the printout. > > Thanks, > > Ingo > > . > I have put this patch into my new patchset, see: http://lkml.org/lkml/2015/2/27/139 [PATCH v3 6/7], and the new patchset has already fixed the problem of 'lack of newline at the end of the printout', see: http://lkml.org/lkml/2015/2/27/140 [PATCH v3 5/7] -- Thanks, Yunlong Song -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/