All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@linux.jf.intel.com>
To: Stephane Eranian <eranian@google.com>
Cc: linux-kernel@vger.kernel.org, peterz@infradead.org,
	mingo@elte.hu, jolsa@redhat.com, zheng.z.yan@intel.com,
	namhyung.kim@lge.com
Subject: Re: [PATCH] perf stat: fix per-socket output bug for uncore events
Date: Fri, 5 Jul 2013 12:12:31 -0700	[thread overview]
Message-ID: <20130705191231.GE5643@tassilo.jf.intel.com> (raw)
In-Reply-To: <20130705170645.GA32519@quad>

> Reported-by: Andi Kleen <ak@linux.intel.com>
> Signed-off-by: Stephane Eranian <eranian@google.com>

Tested-by: Andi Kleen <ak@linux.intel.com>

Works for me. Thanks.

-Andi

  reply	other threads:[~2013-07-05 19:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-05 17:06 [PATCH] perf stat: fix per-socket output bug for uncore events Stephane Eranian
2013-07-05 19:12 ` Andi Kleen [this message]
2013-07-05 20:37 ` Arnaldo Carvalho de Melo
2013-07-12  8:52 ` [tip:perf/urgent] perf stat: Fix " tip-bot for Stephane Eranian

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=20130705191231.GE5643@tassilo.jf.intel.com \
    --to=ak@linux.jf.intel.com \
    --cc=eranian@google.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=namhyung.kim@lge.com \
    --cc=peterz@infradead.org \
    --cc=zheng.z.yan@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.