[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f08ab435-20d9-7fe0-5c0b-bca7d0743c83@linux.intel.com>
Date: Mon, 26 Jun 2017 14:24:29 +0800
From: "Jin, Yao" <yao.jin@...ux.intel.com>
To: Jiri Olsa <jolsa@...hat.com>
Cc: acme@...nel.org, jolsa@...nel.org, peterz@...radead.org,
mingo@...hat.com, alexander.shishkin@...ux.intel.com,
Linux-kernel@...r.kernel.org, ak@...ux.intel.com,
kan.liang@...el.com, yao.jin@...el.com,
linuxppc-dev@...ts.ozlabs.org
Subject: Re: [PATCH v6 0/7] perf report: Show branch type
Hi maintainers,
Is this patch series OK or anything I should update?
Thanks
Jin Yao
On 6/2/2017 4:02 PM, Jin, Yao wrote:
> Hi maintainers,
>
> Is this patch series (v6) OK for merging?
>
> Thanks
>
> Jin Yao
>
>
> On 4/20/2017 5:36 PM, Jiri Olsa wrote:
>> On Thu, Apr 20, 2017 at 08:07:48PM +0800, Jin Yao wrote:
>>> v6:
>>> Update according to the review comments from
>>> Jiri Olsa <jolsa@...hat.com>. Major modifications are:
>>>
>>> 1. Move that multiline conditional code inside {} brackets.
>>>
>>> 2. Move branch_type_stat_display() from builtin-report.c to
>>> branch.c. Move branch_type_str() from callchain.c to
>>> branch.c.
>>>
>>> 3. Keep the original branch info display order, that is:
>>> predicted, abort, cycles, iterations
>> for the tools part
>>
>> Acked-by: Jiri Olsa <jolsa@...nel.org>
>>
>> thanks,
>> jirka
>
Powered by blists - more mailing lists