From: Peter Zijlstra <peterz@infradead.org>
To: Stephane Eranian <eranian@google.com>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu
Subject: Re: [PATCH] perf_event: fix loss of notification with multi-event
Date: Mon, 28 Nov 2011 11:51:25 +0100 [thread overview]
Message-ID: <1322477485.2921.99.camel@twins> (raw)
In-Reply-To: <1322475060.2921.95.camel@twins>
On Mon, 2011-11-28 at 11:11 +0100, Peter Zijlstra wrote:
> OK, I'll stick it in perf/urgent.. Thanks Stephane!
I'll use you as test-subject for my quilt2git script
( http://programming.kicks-ass.net/misc/quilt2git.sh )
My exploded quilt tree lives at:
git://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git
With this particular commit:
http://git.kernel.org/?p=linux/kernel/git/peterz/queue.git;a=commitdiff;h=85d947a9b8113814ee0b8469ff9563d110223874
in the perf/urgent branch.
next prev parent reply other threads:[~2011-11-28 10:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-26 1:47 [PATCH] perf_event: fix loss of notification with multi-event Stephane Eranian
2011-11-28 10:11 ` Peter Zijlstra
2011-11-28 10:51 ` Peter Zijlstra [this message]
2011-11-28 10:56 ` Peter Zijlstra
2011-12-05 13:16 ` [tip:perf/urgent] perf: Fix " tip-bot for Peter Zijlstra
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=1322477485.2921.99.camel@twins \
--to=peterz@infradead.org \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--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