linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Michael Petlan <mpetlan@redhat.com>
Cc: "linux-perf-users@vger.kernel.org" <linux-perf-users@vger.kernel.org>
Subject: Re: [PATCH] perf buildid-list: Fix return value of perf buildid-list -k
Date: Sun, 6 Dec 2015 16:51:40 -0200	[thread overview]
Message-ID: <20151206185140.GD2493@redhat.com> (raw)
In-Reply-To: <1449080871.24573.145.camel@redhat.com>

Em Wed, Dec 02, 2015 at 07:27:51PM +0100, Michael Petlan escreveu:
> The buildid string length is returned by perf buildid-list -k command.
> Since a non-zero return value means an error, perf buildid-list -k cmd
> should return 0 when successful instead.
> 
> Before:
> 
> 	# perf buildid-list -k
> 	39356d74e96e02346fe0ec1f3f162b6c522bac62
> 	# echo $?
> 	41

Thanks, applied.
 
> After:
> 
> 	# perf buildid-list -k
> 	39356d74e96e02346fe0ec1f3f162b6c522bac62
> 	# echo $?
> 	0
> 
> Signed-off-by: Michael Petlan <mpetlan@redhat.com>
> ---
>  tools/perf/builtin-buildid-list.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/tools/perf/builtin-buildid-list.c b/tools/perf/builtin-buildid-list.c
> index 918b4de..6419f57 100644
> --- a/tools/perf/builtin-buildid-list.c
> +++ b/tools/perf/builtin-buildid-list.c
> @@ -110,7 +110,7 @@ int cmd_buildid_list(int argc, const char **argv,
>  	setup_pager();
>  
>  	if (show_kernel)
> -		return sysfs__fprintf_build_id(stdout);
> +		return !(sysfs__fprintf_build_id(stdout) > 0);
>  
>  	return perf_session__list_build_ids(force, with_hits);
>  }
> 

      reply	other threads:[~2015-12-06 18:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-02 18:27 [PATCH] perf buildid-list: Fix return value of perf buildid-list -k Michael Petlan
2015-12-06 18:51 ` Arnaldo Carvalho de Melo [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=20151206185140.GD2493@redhat.com \
    --to=acme@redhat.com \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mpetlan@redhat.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).