From: Frederic Weisbecker <fweisbec@gmail.com>
To: Paul Mundt <lethal@linux-sh.org>
Cc: "K.Prasad" <prasad@linux.vnet.ibm.com>,
Ingo Molnar <mingo@elte.hu>,
Alan Stern <stern@rowland.harvard.edu>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -tip] x86: hw-breakpoints: Actually flush thread breakpoints in flush_thread().
Date: Mon, 19 Oct 2009 21:48:45 +0200 [thread overview]
Message-ID: <20091019194842.GD4880@nowhere> (raw)
In-Reply-To: <20091018062558.GA20535@linux-sh.org>
On Sun, Oct 18, 2009 at 03:25:58PM +0900, Paul Mundt wrote:
> Thanks. If you're setting up a tree somewhere can you let me know where
> it will be hosted? I'm pretty much done with the SH support for the
> existing topic branch in -tip, but if it's being reworked, then I'd like
> to get my changes reworked and integrated as soon as possible.
Oh you have based SH breakpoint support on top of the current breakpoint
API in -tip?
Hm, you should have talked to us about that since it's being reworked.
I'll probably post soon the rebase on top of perf events. And even if
it gets merged in -tip, it should still be considered as very unstable.
May be should you better wait for it to get upstream?
next prev parent reply other threads:[~2009-10-19 19:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-05 10:23 [PATCH -tip] x86: hw-breakpoints: Actually flush thread breakpoints in flush_thread() Paul Mundt
2009-10-05 10:49 ` K.Prasad
2009-10-09 3:40 ` Paul Mundt
2009-10-09 7:53 ` Frederic Weisbecker
2009-10-17 23:42 ` Frederic Weisbecker
2009-10-18 6:25 ` Paul Mundt
2009-10-18 16:43 ` Frederic Weisbecker
2009-10-19 19:48 ` Frederic Weisbecker [this message]
2009-10-19 23:24 ` Paul Mundt
2009-10-20 7:49 ` Frederic Weisbecker
2009-11-21 13:36 ` [tip:perf/core] x86/hw-breakpoints: " tip-bot for Paul Mundt
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=20091019194842.GD4880@nowhere \
--to=fweisbec@gmail.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=prasad@linux.vnet.ibm.com \
--cc=stern@rowland.harvard.edu \
/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.