[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87iopinv33.fsf@sejong.aot.lge.com>
Date: Wed, 07 May 2014 12:09:20 +0900
From: Namhyung Kim <namhyung@...nel.org>
To: Jiri Olsa <jolsa@...hat.com>
Cc: Arnaldo Carvalho de Melo <acme@...nel.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Ingo Molnar <mingo@...nel.org>,
Paul Mackerras <paulus@...ba.org>,
Namhyung Kim <namhyung.kim@....com>,
LKML <linux-kernel@...r.kernel.org>,
David Ahern <dsahern@...il.com>,
Andi Kleen <andi@...stfloor.org>,
Don Zickus <dzickus@...hat.com>
Subject: Re: [PATCHSET 00/17] perf report: Add -F option for specifying output fields (v4)
Hi Jiri,
On Sun, 4 May 2014 19:53:34 +0200, Jiri Olsa wrote:
> On Wed, Apr 16, 2014 at 12:05:37PM +0900, Namhyung Kim wrote:
>
> SNIP
>
>>
>> * changes in v4:
>> - fix a tui navigation bug
>> - fix a bug in output change of perf diff
>> - move call to perf_hpp__init() out of setup_browser()
>> - fix alignment of some output fields on stdio
>>
>> * changes in v3:
>> - rename to --fields option for consistency (David)
>> - prevent to add same keys multiple times
>> - change dso sorting to show unknown dsos last
>> - fix minor bugs
>>
>> * changes in v2:
>> - add a cleanup patch using ui__has_annotation()
>> - cleanup default sort order managment
>> - support perf top also
>> - handle elided sort entries properly
>> - add Acked-by's from Ingo
>>
>>
>> I pushed the patch series on the 'perf/field-v4' branch in my tree
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/namhyung/linux-perf.git
>
> hi,
> I tried to merge this with my latest perf/core and got
> some conflicts. Looks like it's missing the latest hist
> code changes.. could you please rebase?
I can do it maybe next week. But I need to think about the
grouping/hierarchy concept that Don suggested beforehand.
Thanks,
Namhyung
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists