From: "K.Prasad" <prasad@linux.vnet.ibm.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Gene Heskett <gene.heskett@verizon.net>,
Andrew Morton <akpm@linux-foundation.org>,
Alan Stern <stern@rowland.harvard.edu>,
Roland McGrath <roland@redhat.com>,
richardj_moore@uk.ibm.com, jason.wessel@windriver.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Patch 10/10] Sample HW breakpoint over kernel data address
Date: Sun, 15 Feb 2009 15:57:08 +0530 [thread overview]
Message-ID: <20090215102708.GA4154@in.ibm.com> (raw)
In-Reply-To: <20090214224341.GA20477@elte.hu>
On Sat, Feb 14, 2009 at 11:43:41PM +0100, Ingo Molnar wrote:
>
> * K.Prasad <prasad@linux.vnet.ibm.com> wrote:
>
> > On Fri, Feb 13, 2009 at 11:38:41AM -0500, Gene Heskett wrote:
> > > On Friday 13 February 2009, K.Prasad wrote:
> > >
> > > A whole patch series sent as private email, but which should have been
> > > submitted to lkml? Please configure your email agent correctly.
> >
> > I realised that a little late and hence bounced the mails to LKML. It
> > was an oversight on my part, will be more careful henceforth.
>
> Hm, bouncing is not necessarily a good idea, as followups will not have
> lkml Cc:-ed. I'd suggest a repost, with lkml added.
>
> Ingo
Sure. I'm re-posting the patches with LKML included in the recipient.
Thanks,
K.Prasad
next prev parent reply other threads:[~2009-02-15 10:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-13 14:53 [Patch 00/10] Hardware Breakpoint interfaces K.Prasad
2009-02-13 14:54 ` [Patch 1/10] Introducing generic hardware breakpoint handler interfaces K.Prasad
2009-02-13 14:55 ` [Patch 2/10] x86 architecture implementation of Hardware Breakpoint interfaces K.Prasad
2009-02-13 14:55 ` [Patch 3/10] Modifying generic debug exception to use virtual debug registers K.Prasad
2009-02-13 14:56 ` [Patch 4/10] Introduce virtual debug register in thread_struct and wrapper-routines around process related functions K.Prasad
2009-02-13 14:56 ` [Patch 5/10] Use wrapper routines around debug registers in processor " K.Prasad
2009-02-13 14:57 ` [Patch 6/10] Use virtual debug registers in process/thread handling code K.Prasad
2009-02-13 14:58 ` [Patch 7/10] Modify signal handling code to refrain from re-enabling HW Breakpoints K.Prasad
2009-02-13 14:58 ` [Patch 8/10] Modify Ptrace routines to access breakpoint registers K.Prasad
2009-02-13 14:59 ` [Patch 9/10] Cleanup HW Breakpoint registers before kexec K.Prasad
2009-02-13 14:59 ` [Patch 10/10] Sample HW breakpoint over kernel data address K.Prasad
[not found] ` <200902131138.41496.gene.heskett@verizon.net>
[not found] ` <20090214164456.GA5511@in.ibm.com>
[not found] ` <20090214224341.GA20477@elte.hu>
2009-02-15 10:27 ` K.Prasad [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-02-15 10:30 [Patch 00/10] Hardware Breakpoint interfaces K.Prasad
2009-02-15 10:36 ` [Patch 10/10] Sample HW breakpoint over kernel data address K.Prasad
2009-02-10 12:35 [Patch 0/10] Hardware Breakpoint interfaces - v2 K.Prasad
2009-02-10 12:45 ` [Patch 10/10] Sample HW breakpoint over kernel data address K.Prasad
2009-01-29 7:48 [Patch 0/10] Hardware Breakpoint interfaces K.Prasad
2009-01-29 8:31 ` [Patch 10/10] Sample HW breakpoint over kernel data address 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=20090215102708.GA4154@in.ibm.com \
--to=prasad@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=gene.heskett@verizon.net \
--cc=jason.wessel@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=richardj_moore@uk.ibm.com \
--cc=roland@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox