From: Robert Love <rml@tech9.net>
To: Louis Garcia <louisg00@bellsouth.net>
Cc: Rik van Riel <riel@conectiva.com.br>, linux-kernel@vger.kernel.org
Subject: Re: Rik van Riel's vm-rmap
Date: 28 Jan 2002 19:12:45 -0500 [thread overview]
Message-ID: <1012263182.817.9.camel@phantasy> (raw)
In-Reply-To: <1012262826.1634.1.camel@tiger>
In-Reply-To: <Pine.LNX.4.33L.0201280613510.32617-100000@imladris.surriel.com> <1012262826.1634.1.camel@tiger>
On Mon, 2002-01-28 at 19:07, Louis Garcia wrote:
> Does this patch work well with Andrew's low-latency patch?
There will be failed hunks in the VM code (specifically vmscan.c), but
you can safely ignore them. So, yes, it works.
Robert Love
next prev parent reply other threads:[~2002-01-29 0:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-28 4:56 Rik van Riel's vm-rmap Louis Garcia
2002-01-28 5:28 ` William Lee Irwin III
2002-01-28 8:21 ` Rik van Riel
2002-01-29 0:07 ` Louis Garcia
2002-01-29 0:12 ` Robert Love [this message]
2002-01-29 0:14 ` Louis Garcia
2002-01-29 0:15 ` Rik van Riel
2002-01-29 0:56 ` Louis Garcia
2002-01-29 0:19 ` Robert Love
-- strict thread matches above, loose matches on Subject: below --
2002-01-29 1:39 Alex Davis
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=1012263182.817.9.camel@phantasy \
--to=rml@tech9.net \
--cc=linux-kernel@vger.kernel.org \
--cc=louisg00@bellsouth.net \
--cc=riel@conectiva.com.br \
/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