From: Jiri Olsa <jolsa@redhat.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: acme@kernel.org, jolsa@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: perf, tools: Refactor and support interval and CSV metrics
Date: Thu, 10 Mar 2016 12:34:04 +0100 [thread overview]
Message-ID: <20160310113404.GD2617@krava.redhat.com> (raw)
In-Reply-To: <20160307211143.GE5083@two.firstfloor.org>
On Mon, Mar 07, 2016 at 10:11:43PM +0100, Andi Kleen wrote:
SNIP
> >
> > I did not see the change for print_no_aggr_metric function
> > in commit:
> > perf, tools, stat: Add --metric-only support for -A
> >
> > which I saw in the email..
> >
> > however now im confused, I did not noticed I had a wrong tree,
> > however git can't resolve the git tree you mentioned:
>
> I pushed again. Can you try again? Probably I made some mistake with
> git.
I rebased your branch on top of current Arlnaldo's perf/core
and only 3 patches were missing.. I just ack-ed them
thanks,
jirka
next prev parent reply other threads:[~2016-03-10 11:34 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 23:57 perf, tools: Refactor and support interval and CSV metrics Andi Kleen
2016-03-03 23:57 ` [PATCH 1/7] perf, tools, stat: Check existence of frontend/backed stalled cycles Andi Kleen
2016-03-03 23:57 ` [PATCH 2/7] perf, tools, stat: Implement CSV metrics output Andi Kleen
2016-03-03 23:57 ` [PATCH 3/7] perf, tools, stat: Support metrics in --per-core/socket mode Andi Kleen
2016-03-03 23:57 ` [PATCH 4/7] perf, tools, stat: Document CSV format in manpage Andi Kleen
2016-03-10 11:29 ` Jiri Olsa
2016-03-11 8:52 ` [tip:perf/core] perf " tip-bot for Andi Kleen
2016-03-03 23:57 ` [PATCH 5/7] perf, tools, stat: Implement --metric-only mode Andi Kleen
2016-03-10 11:28 ` Jiri Olsa
2016-03-11 8:52 ` [tip:perf/core] perf " tip-bot for Andi Kleen
2016-03-03 23:57 ` [PATCH 6/7] perf, tools, stat: Add --metric-only support for -A Andi Kleen
2016-03-10 11:32 ` Jiri Olsa
2016-03-11 8:52 ` [tip:perf/core] perf " tip-bot for Andi Kleen
2016-03-03 23:57 ` [PATCH 7/7] perf, tools, stat: Check for frontend stalled for metrics Andi Kleen
2016-03-07 10:08 ` perf, tools: Refactor and support interval and CSV metrics Jiri Olsa
2016-03-07 18:22 ` Andi Kleen
2016-03-07 18:48 ` Jiri Olsa
2016-03-07 21:11 ` Andi Kleen
2016-03-10 11:34 ` Jiri Olsa [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-03-03 0:24 Andi Kleen
2016-03-01 18:57 Andi Kleen
2016-03-01 19:05 ` Arnaldo Carvalho de Melo
2016-02-29 22:36 Andi Kleen
2016-03-01 13:07 ` Arnaldo Carvalho de Melo
2016-02-27 0:27 Andi Kleen
2016-02-17 22:43 Andi Kleen
2016-01-30 17:06 Andi Kleen
2016-01-27 0:42 Andi Kleen
2016-01-20 2:26 Andi Kleen
2016-01-22 10:10 ` Jiri Olsa
2016-01-16 1:11 Andi Kleen
2016-01-16 20:21 ` Jiri Olsa
2016-01-18 22:25 ` Andi Kleen
2015-07-30 0:21 Andi Kleen
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=20160310113404.GD2617@krava.redhat.com \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=andi@firstfloor.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.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).