linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Jiri Olsa <jolsa@kernel.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
	David Ahern <dsahern@gmail.com>, Ingo Molnar <mingo@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Markus Trippelsdorf <markus@trippelsdorf.de>
Subject: Re: [PATCH] perf stat: Fix recort_usage typo
Date: Tue, 12 Jan 2016 11:15:37 -0300	[thread overview]
Message-ID: <20160112141537.GR18367@kernel.org> (raw)
In-Reply-To: <1452591329-27620-1-git-send-email-jolsa@kernel.org>

Em Tue, Jan 12, 2016 at 10:35:29AM +0100, Jiri Olsa escreveu:
> Markus reported gcc 6 complains when compiling perf stat command:
> 
>   builtin-stat.c:1591:27: error: ‘recort_usage’ defined but not used
>   [-Werror=unused-const-variable]
>    static const char * const recort_usage[] = {
>                              ^~~~~~~~~~~~
> I fixed the typo and realized we already export record_usage,
> so I also prefixed it with stat (and included report_usage).

Thanks, applied.
 
> Reported-by: Markus Trippelsdorf <markus@trippelsdorf.de>
> Link: http://lkml.kernel.org/n/tip-3c3vkc6bejfsuxxgkcwxllsc@git.kernel.org
> Signed-off-by: Jiri Olsa <jolsa@kernel.org>
> ---
>  tools/perf/builtin-stat.c | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/tools/perf/builtin-stat.c b/tools/perf/builtin-stat.c
> index 7f568244662b..038e877081b6 100644
> --- a/tools/perf/builtin-stat.c
> +++ b/tools/perf/builtin-stat.c
> @@ -1588,7 +1588,7 @@ static int add_default_attributes(void)
>  	return perf_evlist__add_default_attrs(evsel_list, very_very_detailed_attrs);
>  }
>  
> -static const char * const recort_usage[] = {
> +static const char * const stat_record_usage[] = {
>  	"perf stat record [<options>]",
>  	NULL,
>  };
> @@ -1611,7 +1611,7 @@ static int __cmd_record(int argc, const char **argv)
>  	struct perf_session *session;
>  	struct perf_data_file *file = &perf_stat.file;
>  
> -	argc = parse_options(argc, argv, stat_options, record_usage,
> +	argc = parse_options(argc, argv, stat_options, stat_record_usage,
>  			     PARSE_OPT_STOP_AT_NON_OPTION);
>  
>  	if (output_name)
> @@ -1745,7 +1745,7 @@ int process_cpu_map_event(struct perf_tool *tool __maybe_unused,
>  	return set_maps(st);
>  }
>  
> -static const char * const report_usage[] = {
> +static const char * const stat_report_usage[] = {
>  	"perf stat report [<options>]",
>  	NULL,
>  };
> @@ -1779,7 +1779,7 @@ static int __cmd_report(int argc, const char **argv)
>  	struct stat st;
>  	int ret;
>  
> -	argc = parse_options(argc, argv, options, report_usage, 0);
> +	argc = parse_options(argc, argv, options, stat_report_usage, 0);
>  
>  	if (!input_name || !strlen(input_name)) {
>  		if (!fstat(STDIN_FILENO, &st) && S_ISFIFO(st.st_mode))
> -- 
> 2.4.3

  reply	other threads:[~2016-01-12 14:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-12  9:35 [PATCH] perf stat: Fix recort_usage typo Jiri Olsa
2016-01-12 14:15 ` Arnaldo Carvalho de Melo [this message]
2016-01-13  9:39 ` [tip:perf/urgent] " tip-bot for Jiri Olsa

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=20160112141537.GR18367@kernel.org \
    --to=acme@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=dsahern@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markus@trippelsdorf.de \
    --cc=mingo@kernel.org \
    --cc=namhyung@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).