[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200402160049.GE8736@kernel.org>
Date: Thu, 2 Apr 2020 13:00:49 -0300
From: Arnaldo Carvalho de Melo <arnaldo.melo@...il.com>
To: "Liang, Kan" <kan.liang@...ux.intel.com>
Cc: Jiri Olsa <jolsa@...hat.com>, peterz@...radead.org,
mingo@...hat.com, linux-kernel@...r.kernel.org,
namhyung@...nel.org, adrian.hunter@...el.com,
mathieu.poirier@...aro.org, ravi.bangoria@...ux.ibm.com,
alexey.budankov@...ux.intel.com, vitaly.slobodskoy@...el.com,
pavel.gerasimov@...el.com, mpe@...erman.id.au, eranian@...gle.com,
ak@...ux.intel.com
Subject: Re: [PATCH V4 00/17] Stitch LBR call stack (Perf Tools)
Em Thu, Apr 02, 2020 at 11:34:18AM -0400, Liang, Kan escreveu:
>
>
> On 3/23/2020 7:13 AM, Jiri Olsa wrote:
> > On Thu, Mar 19, 2020 at 01:25:00PM -0700, kan.liang@...ux.intel.com wrote:
> > > From: Kan Liang <kan.liang@...ux.intel.com>
> > >
> > > Changes since V3:
> > > - There is no dependency among the 'capabilities'. If perf fails to read
> > > one, it should not impact others. Continue to parse the rest of caps.
> > > (Patch 1)
> > > - Use list_for_each_entry() to replace perf_pmu__scan_caps() (Patch 1 &
> > > 2)
> > > - Combine the declaration plus assignment when possible (Patch 1 & 2)
> > > - Add check for script/report/c2c.. (Patch 13, 14 & 16)
> >
> > it's all black magic to me, but looks ok ;-)
> >
> > Acked-by: Jiri Olsa <jolsa@...hat.com>
> >
>
> Thanks Jirka.
>
> Hi Arnaldo,
>
> Any comments for the series?
I need to test it, hope to do it soon, but I'm a bit backlogged, sorry.
- Arnaldo
Powered by blists - more mailing lists