From: "Raphaël Beamonte" <raphael.beamonte@gmail.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: "Raphaël Beamonte" <raphael.beamonte@gmail.com>,
"Peter Zijlstra" <a.p.zijlstra@chello.nl>,
"Ingo Molnar" <mingo@redhat.com>, "Jiri Olsa" <jolsa@kernel.org>,
"Adrian Hunter" <adrian.hunter@intel.com>,
"Yunlong Song" <yunlong.song@huawei.com>,
"Matt Fleming" <matt.fleming@intel.com>,
"Kan Liang" <kan.liang@intel.com>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Namhyung Kim" <namhyung@kernel.org>,
"Hemant Kumar" <hemant@linux.vnet.ibm.com>,
"Masami Hiramatsu" <masami.hiramatsu.pt@hitachi.com>,
"Wang Nan" <wangnan0@huawei.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH] perf: bugzilla 100781
Date: Sun, 16 Aug 2015 21:39:11 -0400 [thread overview]
Message-ID: <cover.1439775095.git.raphael.beamonte@gmail.com> (raw)
Hi,
I tried myself at solving the bugzilla report 100781 that can be
found here: https://bugzilla.kernel.org/show_bug.cgi?id=100781
You'll find in the following email the patch I did for that.
I welcome any advice or remarks (or insults, but please be gentle,
I'm still a newbie!) to make that patch better in hope that it
could be used upstream and thus close that bug report!
Thanks,
Raphaël
Raphaël Beamonte (1):
perf: fix confusing messages when not able to read trace events files
tools/perf/util/parse-events.c | 14 +++++++++++---
tools/perf/util/parse-options.c | 6 ++++++
2 files changed, 17 insertions(+), 3 deletions(-)
--
2.1.4
next reply other threads:[~2015-08-17 1:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-17 1:39 Raphaël Beamonte [this message]
2015-08-17 1:39 ` [PATCH] perf: fix confusing messages when not able to read trace events files Raphaël Beamonte
2015-08-18 11:43 ` Matt Fleming
2015-08-18 17:45 ` Raphaël Beamonte
2015-08-20 13:52 ` Matt Fleming
2015-08-24 20:51 ` 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=cover.1439775095.git.raphael.beamonte@gmail.com \
--to=raphael.beamonte@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=hemant@linux.vnet.ibm.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=matt.fleming@intel.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=rostedt@goodmis.org \
--cc=wangnan0@huawei.com \
--cc=yunlong.song@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