From: Michael Petlan <mpetlan@redhat.com>
To: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: "Jiri Olsa" <jolsa@redhat.com>,
"平松雅巳 / HIRAMATU，MASAMI" <masami.hiramatsu.pt@hitachi.com>,
"linux-perf-users@vger.kernel.org"
<linux-perf-users@vger.kernel.org>
Subject: [PATCH] perf buildid-list: Show running kernel build id fix
Date: Fri, 27 Nov 2015 14:48:03 +0100 [thread overview]
Message-ID: <1448632083.24573.113.camel@redhat.com> (raw)
Hi all,
I have noticed that the '--kernel' option of perf buildid-list
tool has been broken, so no buildid is printed.
The attached patch should address the issue.
I have tested it against the latest version of Linus' tree.
Nothing wrong should be caused by this change, since in the
other cases when the function is called, no one cares about
the return value.
Michael
Michael Petlan (1):
perf buildid-list: Show running kernel build id fix
tools/perf/util/build-id.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
next reply other threads:[~2015-11-27 13:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-27 13:48 Michael Petlan [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-11-27 13:48 [PATCH] perf buildid-list: Show running kernel build id fix Michael Petlan
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=1448632083.24573.113.camel@redhat.com \
--to=mpetlan@redhat.com \
--cc=acme@redhat.com \
--cc=jolsa@redhat.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.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).