From: "Vamsi Krishna S ." <vamsi@in.ibm.com>
To: Arjan van de Ven <arjanv@redhat.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
rusty@rustcorp.com.au, richard <richardj_moore@uk.ibm.com>,
suparna@in.ibm.com, bharata <bharata@in.ibm.com>
Subject: Re: [patch 1/4] kprobes - base for 2.5.44
Date: Tue, 22 Oct 2002 17:32:44 +0530 [thread overview]
Message-ID: <20021022173244.A26805@in.ibm.com> (raw)
In-Reply-To: <1035287010.3002.4.camel@localhost.localdomain>; from arjanv@redhat.com on Tue, Oct 22, 2002 at 01:43:29PM +0200
Arjan,
I understand your point, I will post all patches in a series in a
single thread in future.
Thanks,
--
Vamsi Krishna S.
Linux Technology Center,
IBM Software Lab, Bangalore.
Ph: +91 80 5044959
Internet: vamsi@in.ibm.com
next prev parent reply other threads:[~2002-10-22 11:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-22 11:09 [patch 1/4] kprobes - base for 2.5.44 Vamsi Krishna S .
2002-10-22 11:43 ` Arjan van de Ven
2002-10-22 12:02 ` Vamsi Krishna S . [this message]
2002-10-22 12:16 ` Alan Cox
2002-10-23 1:07 ` Rusty Russell
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=20021022173244.A26805@in.ibm.com \
--to=vamsi@in.ibm.com \
--cc=arjanv@redhat.com \
--cc=bharata@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=richardj_moore@uk.ibm.com \
--cc=rusty@rustcorp.com.au \
--cc=suparna@in.ibm.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).