public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: acme@kernel.org, jolsa@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: perf: Improve support for uncore JSON event lists
Date: Mon, 13 Mar 2017 17:15:45 +0100	[thread overview]
Message-ID: <20170313161545.GA27212@krava> (raw)
In-Reply-To: <20170313161141.GA14380@two.firstfloor.org>

On Mon, Mar 13, 2017 at 09:11:42AM -0700, Andi Kleen wrote:
> > > Available from
> > > 
> > > git://git.kernel.org/pub/scm/linux/kernel/git/ak/linux-misc.git perf/builtin-json-29
> > 
> > hi,
> > I can't see the branch..
> 
> It's there
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/ak/linux-misc.git/log/?h=perf/builtin-json-29
> 
> -Andi


you mean you just pushed it? ;-)

jirka

[jolsa@krava linux-perf]$ git remote update ak
Fetching ak
remote: Counting objects: 136, done.
remote: Compressing objects: 100% (47/47), done.
remote: Total 136 (delta 118), reused 107 (delta 89)
Receiving objects: 100% (136/136), 25.58 KiB | 0 bytes/s, done.
Resolving deltas: 100% (118/118), completed with 34 local objects.
>From git://git.kernel.org/pub/scm/linux/kernel/git/ak/linux-misc
 * [new branch]                perf/builtin-json-29 -> ak/perf/builtin-json-29

  reply	other threads:[~2017-03-13 16:15 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-10 21:24 perf: Improve support for uncore JSON event lists Andi Kleen
2017-03-10 21:24 ` [PATCH 01/13] perf, tools, stat: Factor out callback for collecting event values Andi Kleen
2017-03-14 14:56   ` Jiri Olsa
2017-03-10 21:24 ` [PATCH 02/13] perf, tools, stat: Collapse identically named events Andi Kleen
2017-03-10 21:24 ` [PATCH 03/13] perf, tools, stat: Handle partially bad results with merging Andi Kleen
2017-03-10 21:24 ` [PATCH 04/13] perf, tools: Factor out PMU matching in parser Andi Kleen
2017-03-10 21:24 ` [PATCH 05/13] perf, tools: Expand PMU events by prefix match Andi Kleen
2017-03-10 21:24 ` [PATCH 06/13] perf, tools: Special case uncore_ prefix Andi Kleen
2017-03-10 21:24 ` [PATCH 07/13] perf, tools: Add a simple expression parser for JSON Andi Kleen
2017-03-10 21:24 ` [PATCH 08/13] perf, tools: Update Intel uncore JSON event files Andi Kleen
2017-03-10 21:24 ` [PATCH 09/13] perf, tools: Support MetricExpr header in JSON event list Andi Kleen
2017-03-10 21:24 ` [PATCH 10/13] perf, tools, stat: Output JSON MetricExpr metric Andi Kleen
2017-03-10 21:24 ` [PATCH 11/13] perf, tools, list: Support printing MetricExpr with --debug Andi Kleen
2017-03-10 21:24 ` [PATCH 12/13] perf, tools: Add support for MetricName JSON attribute Andi Kleen
2017-03-10 21:24 ` [PATCH 13/13] perf, tools, list: Move extra details printing to new option Andi Kleen
2017-03-13 14:43 ` perf: Improve support for uncore JSON event lists Jiri Olsa
2017-03-13 16:11   ` Andi Kleen
2017-03-13 16:15     ` Jiri Olsa [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-03-20 20:16 Andi Kleen
2017-03-21 14:48 ` Jiri Olsa
2017-03-21 19:53   ` Arnaldo Carvalho de Melo
2017-03-01  6:49 Andi Kleen
2017-03-07 10:04 ` Jiri Olsa

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=20170313161545.GA27212@krava \
    --to=jolsa@redhat.com \
    --cc=acme@kernel.org \
    --cc=andi@firstfloor.org \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.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