From: Rik van Riel <H.H.vanRiel@phys.uu.nl>
To: "Benjamin C.R. LaHaise" <blah@kvack.org>
Cc: linux-mm <linux-mm@kvack.org>
Subject: Re: I've got some patches to integrate... (fwd)
Date: Wed, 15 Apr 1998 18:08:05 +0200 (MET DST) [thread overview]
Message-ID: <Pine.LNX.3.91.980415180555.17965A-100000@mirkwood.dummy.home> (raw)
In-Reply-To: <Pine.LNX.3.95.980415112011.839G-100000@as200.spellcast.com>
On Wed, 15 Apr 1998, Benjamin C.R. LaHaise wrote:
> Hmmm, before I make any silly mumblings, would you mind [re]sending a copy
> of your patch to linux-mm? (I've misplaced the copy I had, and linuxhq's
> kernel archive isn't searchable right now.) Linus probably won't want to
> integrate them for 2.2, but perhaps we can start maintaining a set of
> patches reasonably 'in sync' until 2.3 when they could be integrated.
If you make a page like that, please send me a pointer so I
can include it on my memory-management patches page (which
is accessible from LinuxHQ!).
> Which reminds me: Stephen, what's the state of your irq and smp patches
> for page cache addition/removal. I'm getting a bit more free time now, so
> perhaps I can play with them a bit (maybe we should have a common cvs
> tree...).
A common tree would be nice too. Possibly with a 'bigmama'-like
patch for the MM system...
Rik.
+-------------------------------------------+--------------------------+
| Linux: - LinuxHQ MM-patches page | Scouting webmaster |
| - kswapd ask-him & complain-to guy | Vries cubscout leader |
| http://www.phys.uu.nl/~riel/ | <H.H.vanRiel@phys.uu.nl> |
+-------------------------------------------+--------------------------+
parent reply other threads:[~1998-04-15 16:08 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <Pine.LNX.3.95.980415112011.839G-100000@as200.spellcast.com>]
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=Pine.LNX.3.91.980415180555.17965A-100000@mirkwood.dummy.home \
--to=h.h.vanriel@phys.uu.nl \
--cc=blah@kvack.org \
--cc=linux-mm@kvack.org \
/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