From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: kaustav.majumdar@wipro.com
Cc: penberg@cs.helsinki.fi, linux-mm@kvack.org
Subject: RE: Memory Leak Detection and Kernel Memory monitoring tool
Date: Fri, 16 Jun 2006 14:12:32 +0200 [thread overview]
Message-ID: <1150459952.28517.2.camel@lappy> (raw)
In-Reply-To: <05B7784238A51247A0A9FB4B348CECAE01D768E5@PNE-HJN-MBX01.wipro.com>
> Actually I was trying for 2.6.15.4.
Why don't you develop against the latest kernel, with all the nice new
features you want? This is easier for upstream submission too.
If you really want your kernel-driver to work for this old kernel, back
port it when it proves itself stable.
Peter
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2006-06-16 12:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-16 11:39 kaustav.majumdar
2006-06-16 12:12 ` Peter Zijlstra [this message]
2006-06-16 12:48 ` Pekka Enberg
[not found] <AcaRI8wQZTxlnEvkSZKzcK/VjpZN+AACMtwA>
2006-06-16 10:13 ` kaustav.majumdar
2006-06-16 11:20 ` Pekka Enberg
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=1150459952.28517.2.camel@lappy \
--to=a.p.zijlstra@chello.nl \
--cc=kaustav.majumdar@wipro.com \
--cc=linux-mm@kvack.org \
--cc=penberg@cs.helsinki.fi \
/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