linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Stephane Eranian <eranian@google.com>
Cc: linux-kernel@vger.kernel.org, peterz@infradead.org,
	mingo@kernel.org, linux-perf-users@vger.kernel.org
Subject: Re: [PATCH] perf tools: update quipper information
Date: Thu, 8 Mar 2018 11:14:43 -0300	[thread overview]
Message-ID: <20180308141443.GB2187@redhat.com> (raw)
In-Reply-To: <1520495985-2147-1-git-send-email-eranian@google.com>

Em Wed, Mar 07, 2018 at 11:59:45PM -0800, Stephane Eranian escreveu:
> This patch updates the links to the Quipper library.
> It is now available from GitHub and has been updated.

Thanks, applied.

- Arnaldo
 
> Reported-by: Lakshman Annadorai <lakshmana@google.com>
> Signed-off-by: Stephane Eranian <eranian@google.com>
> ---
>  tools/perf/Documentation/perf.data-file-format.txt | 7 +------
>  1 file changed, 1 insertion(+), 6 deletions(-)
> 
> diff --git a/tools/perf/Documentation/perf.data-file-format.txt b/tools/perf/Documentation/perf.data-file-format.txt
> index f7d85e89a98a..d00f0d51cab8 100644
> --- a/tools/perf/Documentation/perf.data-file-format.txt
> +++ b/tools/perf/Documentation/perf.data-file-format.txt
> @@ -485,10 +485,5 @@ in pmu-tools parser. This allows to read perf.data from python and dump it.
>  quipper
>  
>  The quipper C++ parser is available at
> -https://chromium.googlesource.com/chromiumos/platform2
> +http://github.com/google/perf_data_converter/tree/master/src/quipper
>  
> -It is under the chromiumos-wide-profiling/ subdirectory. This library can
> -convert a perf data file to a protobuf and vice versa.
> -
> -Unfortunately this parser tends to be many versions behind and may not be able
> -to parse data files generated by recent perf.
> -- 
> 2.7.4

           reply	other threads:[~2018-03-08 14:14 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1520495985-2147-1-git-send-email-eranian@google.com>]

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=20180308141443.GB2187@redhat.com \
    --to=acme@redhat.com \
    --cc=eranian@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).