From: Jiri Olsa <jolsa@kernel.org>
To: Arnaldo Carvalho de Melo <acme@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>
Subject: [PATCH 0/7] perf tools: Move sort bools into struct perf_hpp_list
Date: Tue, 3 May 2016 13:54:41 +0200 [thread overview]
Message-ID: <1462276488-26683-1-git-send-email-jolsa@kernel.org> (raw)
hi,
now we have sort dimensions private for struct hists,
we need to make dimension booleans hists specific as
well.
Also available in here:
git://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git
perf/fixes
thanks,
jirka
---
Jiri Olsa (7):
perf tools: Move sort__need_collapse into struct perf_hpp_list
perf tools: Move sort__has_parent into struct perf_hpp_list
perf tools: Move sort__has_sym into struct perf_hpp_list
perf tools: Move sort__has_dso into struct perf_hpp_list
perf tools: Move sort__has_socket into struct perf_hpp_list
perf tools: Move sort__has_thread into struct perf_hpp_list
perf tools: Move sort__has_comm into struct perf_hpp_list
tools/perf/builtin-diff.c | 4 ++--
tools/perf/builtin-report.c | 4 ++--
tools/perf/builtin-top.c | 8 ++++----
tools/perf/tests/hists_common.c | 2 +-
tools/perf/tests/hists_cumulate.c | 2 +-
tools/perf/tests/hists_link.c | 4 ++--
tools/perf/tests/hists_output.c | 2 +-
tools/perf/ui/browsers/hists.c | 32 +++++++++++++++++---------------
tools/perf/ui/gtk/hists.c | 2 +-
tools/perf/ui/hist.c | 2 +-
tools/perf/util/annotate.c | 2 +-
tools/perf/util/callchain.c | 2 +-
tools/perf/util/hist.c | 14 +++++++-------
tools/perf/util/hist.h | 10 ++++++++++
tools/perf/util/machine.c | 2 +-
tools/perf/util/sort.c | 35 ++++++++++++++---------------------
tools/perf/util/sort.h | 7 -------
17 files changed, 66 insertions(+), 68 deletions(-)
next reply other threads:[~2016-05-03 11:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-03 11:54 Jiri Olsa [this message]
2016-05-03 11:54 ` [PATCH 1/7] perf tools: Move sort__need_collapse into struct perf_hpp_list Jiri Olsa
2016-05-06 6:42 ` [tip:perf/core] perf hists: " tip-bot for Jiri Olsa
2016-05-03 11:54 ` [PATCH 2/7] perf tools: Move sort__has_parent " Jiri Olsa
2016-05-06 6:42 ` [tip:perf/core] perf hists: " tip-bot for Jiri Olsa
2016-05-03 11:54 ` [PATCH 3/7] perf tools: Move sort__has_sym " Jiri Olsa
2016-05-06 6:42 ` [tip:perf/core] perf hists: " tip-bot for Jiri Olsa
2016-05-03 11:54 ` [PATCH 4/7] perf tools: Move sort__has_dso " Jiri Olsa
2016-05-06 6:43 ` [tip:perf/core] perf hists: " tip-bot for Jiri Olsa
2016-05-03 11:54 ` [PATCH 5/7] perf tools: Move sort__has_socket " Jiri Olsa
2016-05-06 6:43 ` [tip:perf/core] perf hists: " tip-bot for Jiri Olsa
2016-05-03 11:54 ` [PATCH 6/7] perf tools: Move sort__has_thread " Jiri Olsa
2016-05-06 6:44 ` [tip:perf/core] perf hists: " tip-bot for Jiri Olsa
2016-05-03 11:54 ` [PATCH 7/7] perf tools: Move sort__has_comm " Jiri Olsa
2016-05-06 6:44 ` [tip:perf/core] perf hists: " 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=1462276488-26683-1-git-send-email-jolsa@kernel.org \
--to=jolsa@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=dsahern@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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).