From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Lin Ming <ming.m.lin@intel.com>
Cc: Ingo Molnar <mingo@elte.hu>, Andi Kleen <andi@firstfloor.org>,
Stephane Eranian <eranian@google.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 0/4] perf: offcore event monitoring patches
Date: Thu, 03 Mar 2011 11:14:57 +0100 [thread overview]
Message-ID: <1299147297.1310.50.camel@laptop> (raw)
In-Reply-To: <1299119690-13991-1-git-send-email-ming.m.lin@intel.com>
On Thu, 2011-03-03 at 10:34 +0800, Lin Ming wrote:
> Peter,
> The event scheduling issue was fixed, could you please consider merging
> this series?
I'll have a look today.
BTW, you managed to wreck git-send-email, you have git 1.7 which does
the right thing by default (--no-chain-reply-to), please do use that. I
normally ignore emails send like this.
next prev parent reply other threads:[~2011-03-03 10:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-03 2:34 Lin Ming
2011-03-03 2:34 ` [PATCH v3 1/4] perf: Add support for supplementary event registers Lin Ming
2011-03-03 2:34 ` [PATCH v3 2/4] perf: Fix LLC-* events on Intel Nehalem/Westmere Lin Ming
2011-03-03 2:34 ` [PATCH v3 3/4] perf: Add support to the perf tool to specify extra values Lin Ming
2011-03-03 2:34 ` [PATCH v3 4/4] perf: Avoid the percore allocations if HT is not capable Lin Ming
2011-03-04 13:04 ` [tip:perf/core] perf: Avoid the percore allocations if the CPU is not HT capable tip-bot for Lin Ming
2011-03-05 15:52 ` tip-bot for Lin Ming
2011-03-04 11:53 ` [tip:perf/core] perf: Fix LLC-* events on Intel Nehalem/Westmere tip-bot for Andi Kleen
2011-05-06 9:43 ` [tip:perf/urgent] perf events, x86: Fix Intel Nehalem and Westmere last level cache event definitions tip-bot for Peter Zijlstra
2011-03-04 11:53 ` [tip:perf/core] perf: Add support for supplementary event registers tip-bot for Andi Kleen
2011-03-03 10:14 ` Peter Zijlstra [this message]
2011-03-04 1:16 ` [PATCH v3 0/4] perf: offcore event monitoring patches Lin Ming
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=1299147297.1310.50.camel@laptop \
--to=a.p.zijlstra@chello.nl \
--cc=andi@firstfloor.org \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.m.lin@intel.com \
--cc=mingo@elte.hu \
/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
all inboxes | Powered by JetHome®