From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Stephane Eranian <eranian@google.com>
Cc: Steve MacLean <Steve.MacLean@microsoft.com>,
Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
Eric Saint-Etienne <eric.saint.etienne@oracle.com>,
John Keeping <john@metanate.com>, Andi Kleen <ak@linux.intel.com>,
Song Liu <songliubraving@fb.com>,
Davidlohr Bueso <dave@stgolabs.net>, Leo Yan <leo.yan@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Brian Robbins <brianrob@microsoft.com>,
Tom McDonald <Thomas.McDonald@microsoft.com>,
John Salem <josalem@microsoft.com>
Subject: Re: [PATCH 4/4] perf docs: Correct and clarify jitdump spec
Date: Mon, 30 Sep 2019 07:48:43 -0300 [thread overview]
Message-ID: <20190930104843.GC9622@kernel.org> (raw)
In-Reply-To: <CABPqkBTVso=2bo1EkYETXBOk_g1ykiZdHcQmt9uew5JECQzEBw@mail.gmail.com>
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@microsoft.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@google.com>
Thanks, applied.
- Arnaldo
prev parent reply other threads:[~2019-09-30 10:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-28 1:53 [PATCH 4/4] perf docs: Correct and clarify jitdump spec Steve MacLean
2019-09-28 4:39 ` Stephane Eranian
2019-09-30 10:48 ` Arnaldo Carvalho de Melo [this message]
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=20190930104843.GC9622@kernel.org \
--to=arnaldo.melo@gmail.com \
--cc=Steve.MacLean@microsoft.com \
--cc=Thomas.McDonald@microsoft.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=brianrob@microsoft.com \
--cc=dave@stgolabs.net \
--cc=eranian@google.com \
--cc=eric.saint.etienne@oracle.com \
--cc=john@metanate.com \
--cc=jolsa@redhat.com \
--cc=josalem@microsoft.com \
--cc=leo.yan@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=songliubraving@fb.com \
/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