linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Benjamin C.R. LaHaise" <blah@kvack.org>
To: "Eric W. Biederman" <ebiederm+eric@npwt.net>
Cc: linux-mm@kvack.org
Subject: Re: I've got some patches to integrate...
Date: Wed, 15 Apr 1998 11:11:07 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.3.95.980415105437.839D-100000@as200.spellcast.com> (raw)
In-Reply-To: <m11zuz4vm5.fsf@flinx.npwt.net>

Hello Eric,

On 14 Apr 1998, Eric W. Biederman wrote:
...
> Anyhow I thought I'd bounce off what I had off this list and see what
> people thought of my ideas.  I started checking with Stepen Tweedie to
> see if he maintained the swap code and if I should send patches to
> him, or Linus.  And he said it should bounce what I have off of this
> list, and to start talks about integrating it.
...

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. 
Hopefully that way they we can get people to provide a reasonable amount
of testing to the code. 

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...).

		-ben

  reply	other threads:[~1998-04-15 15:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-04-15  3:22 Eric W. Biederman
1998-04-15 15:11 ` Benjamin C.R. LaHaise [this message]
1998-04-15 17:58   ` Eric W. Biederman
1998-04-20 21:55   ` I've got some patches to integrate, too Stephen C. Tweedie

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.980415105437.839D-100000@as200.spellcast.com \
    --to=blah@kvack.org \
    --cc=ebiederm+eric@npwt.net \
    --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