linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Benjamin C.R. LaHaise" <blah@kvack.org>
To: linux-kernel@vger.rutgers.edu
Cc: linux-mm@kvack.org
Subject: Re: [patch] my latest oom stuff
Date: Fri, 30 Oct 1998 10:39:26 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.3.95.981030103318.169A-100000@as200.spellcast.com> (raw)
In-Reply-To: <Pine.LNX.3.96.981030144018.999A-100000@dragon.bogus>

On Fri, 30 Oct 1998, Andrea Arcangeli wrote:

> Ok the last patch (the one with the FP_* flags) seems really perfect. I
> have put out a new whole patch against pre-2.1.127-2 (with the
> swap_duplicate() bogus check removed). 
> 
> ftp://e-mind.com/pub/linux/kernel-patches/oom-22...

For those of you having trouble getting to e-mind.com (70% loss from
here...), I've put a copy at:
http://www.kvack.org/~blah/patches/andrea-oom-22-pre-2.1.127-2.diff.gz

		-ben

--
This is a majordomo managed list.  To unsubscribe, send a message with
the body 'unsubscribe linux-mm me@address' to: majordomo@kvack.org

           reply	other threads:[~1998-10-30 15:39 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <Pine.LNX.3.96.981030144018.999A-100000@dragon.bogus>]

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.95.981030103318.169A-100000@as200.spellcast.com \
    --to=blah@kvack.org \
    --cc=linux-kernel@vger.rutgers.edu \
    --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