[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190930104843.GC9622@kernel.org>
Date: Mon, 30 Sep 2019 07:48:43 -0300
From: Arnaldo Carvalho de Melo <arnaldo.melo@...il.com>
To: Stephane Eranian <eranian@...gle.com>
Cc: Steve MacLean <Steve.MacLean@...rosoft.com>,
Arnaldo Carvalho de Melo <arnaldo.melo@...il.com>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>,
Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Jiri Olsa <jolsa@...hat.com>,
Namhyung Kim <namhyung@...nel.org>,
Eric Saint-Etienne <eric.saint.etienne@...cle.com>,
John Keeping <john@...anate.com>,
Andi Kleen <ak@...ux.intel.com>,
Song Liu <songliubraving@...com>,
Davidlohr Bueso <dave@...olabs.net>,
Leo Yan <leo.yan@...aro.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Brian Robbins <brianrob@...rosoft.com>,
Tom McDonald <Thomas.McDonald@...rosoft.com>,
John Salem <josalem@...rosoft.com>
Subject: Re: [PATCH 4/4] perf docs: Correct and clarify jitdump spec
Em Fri, Sep 27, 2019 at 09:39:00PM -0700, Stephane Eranian escreveu:
> On Fri, Sep 27, 2019 at 6:53 PM Steve MacLean
> <Steve.MacLean@...rosoft.com> wrote:
> >
> > Specification claims latest version of jitdump file format is 2. Current
> > jit dump reading code treats 1 as the latest version.
> >
> > Correct spec to match code.
<SNIP>
> Corrections are valid.
>
> Acked-by: Stephane Eranian <eranian@...gle.com>
Thanks, applied.
- Arnaldo
Powered by blists - more mailing lists