From: Peter Zijlstra <peterz@infradead.org>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>,
prasad.krishnan@gmail.com, linux-kernel@vger.kernel.org,
mingo@redhat.com, paulus@samba.org, acme@ghostprotocols.net,
emachado@linux.vnet.ibm.com
Subject: Re: [PATCH v3] Hardware breakpoints: Invoke __perf_event_disable() if interrupts are already disabled
Date: Thu, 16 Aug 2012 10:16:59 +0200 [thread overview]
Message-ID: <1345105019.29668.0.camel@twins> (raw)
In-Reply-To: <20120815184216.GC19716@somewhere>
On Wed, 2012-08-15 at 20:42 +0200, Frederic Weisbecker wrote:
> On Wed, Aug 15, 2012 at 11:07:01PM +0530, Naveen N. Rao wrote:
> > Hi Frederick,
> > Did you get a chance to take a look at this?
> >
> > Regards,
> > Naveen
>
> Yeah, I'm ok with the patch. Peter, are you ok with it?
Yeah, queued, it. sorry for loosing track etc..
next prev parent reply other threads:[~2012-08-16 8:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 6:02 [Patch][perf] Invoke __perf_event_disable without an IPI K.Prasad
2012-06-11 11:13 ` Peter Zijlstra
2012-06-12 6:06 ` K.Prasad
2012-06-12 9:12 ` Peter Zijlstra
2012-07-06 9:52 ` [PATCH v2] Hardware breakpoints: Invoke __perf_event_disable() if interrupts are already disabled Naveen N. Rao
2012-07-06 10:18 ` Naveen N. Rao
2012-07-18 10:30 ` [PATCH v2 RESEND] " Naveen N. Rao
2012-07-18 11:57 ` Frederic Weisbecker
2012-07-19 11:16 ` Naveen N. Rao
2012-07-25 11:32 ` Naveen N. Rao
2012-07-31 13:41 ` Frederic Weisbecker
2012-08-02 8:16 ` [PATCH v3] " Naveen N. Rao
2012-08-15 17:37 ` Naveen N. Rao
2012-08-15 18:42 ` Frederic Weisbecker
2012-08-16 8:16 ` Peter Zijlstra [this message]
2012-08-29 2:45 ` Naveen N. Rao
2012-09-04 18:53 ` [tip:perf/urgent] perf/hwpb: " tip-bot for K.Prasad
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=1345105019.29668.0.camel@twins \
--to=peterz@infradead.org \
--cc=acme@ghostprotocols.net \
--cc=emachado@linux.vnet.ibm.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--cc=paulus@samba.org \
--cc=prasad.krishnan@gmail.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 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).