From: Jens Axboe <axboe@suse.de>
To: Andrew Morton <akpm@zip.com.au>
Cc: "Ken Brownfield" <brownfld@irridia.com>,
"Dieter Nützel" <Dieter.Nuetzel@hamburg.de>,
"Linux Kernel List" <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.19-preX: What we really need: -AA patches finally in the tree
Date: Tue, 26 Feb 2002 08:20:21 +0100 [thread overview]
Message-ID: <20020226072021.GC11837@suse.de> (raw)
In-Reply-To: <200202260135.18913.Dieter.Nuetzel@hamburg.de> <20020225190241.C26077@asooo.flowerfire.com> <3C7AE123.97A92EA0@zip.com.au>
In-Reply-To: <3C7AE123.97A92EA0@zip.com.au>
On Mon, Feb 25 2002, Andrew Morton wrote:
> Ken Brownfield wrote:
> >
> > ...
> > It should be in it's own release separate from other major changes at
> > least, IMHO, if the backport is desired by enough folk to outweigh the
> > largish change. And I definitely have VM _way_ higher up my personal
> > list. :)
> >
>
> I intend to chunk up the -aa VM patch and feed it into 2.4.19-pre.
> I think Andrea's OK with that. Just the VM and buffercache bits.
> Something also needs to be done about block-highmem and pte-highmem.
I've recommended block-highmem before, and I can do it again. If it
needs to be split a bit (I don't really think it does, though), I can
even do that too.
--
Jens Axboe
next prev parent reply other threads:[~2002-02-26 7:21 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-26 0:35 2.4.19-preX: What we really need: -AA patches finally in the tree Dieter Nützel
2002-02-26 1:02 ` Ken Brownfield
2002-02-26 1:13 ` Andrew Morton
2002-02-26 7:20 ` Jens Axboe [this message]
2002-02-26 1:39 ` Alan Cox
2002-02-26 1:15 ` Shawn Starr
2002-02-26 1:32 ` Martin J. Bligh
2002-02-24 5:44 ` Daniel Phillips
2002-02-26 4:33 ` Martin J. Bligh
2002-02-26 11:42 ` Rik van Riel
2002-02-26 1:40 ` Rik van Riel
2002-02-26 1:49 ` Martin J. Bligh
2002-02-26 1:51 ` Alan Cox
2002-02-26 8:36 ` Christoph Rohland
2002-02-26 7:07 ` Christoph Hellwig
2002-02-26 16:21 ` Mike Fedyk
2002-02-26 16:53 ` Christoph Hellwig
2002-02-28 22:45 ` Bill Davidsen
2002-02-28 23:04 ` Rik van Riel
2002-03-01 1:04 ` 2.4.19-preX: What we really need: -AA patches finally in the Alan Cox
2002-03-01 1:14 ` Rik van Riel
2002-03-01 3:02 ` 2.4.19-preX: What we really need: -AA patches finally in the tree Bill Davidsen
2002-03-01 3:13 ` Rik van Riel
2002-03-01 3:43 ` Davide Libenzi
2002-03-01 10:36 ` Sean Hunter
2002-03-01 17:13 ` Davide Libenzi
2002-03-01 6:29 ` Olivier Galibert
2002-03-01 16:28 ` Dan Chen
-- strict thread matches above, loose matches on Subject: below --
2002-03-01 6:41 dart
2002-03-05 21:49 ` Bill Davidsen
2002-03-06 1:05 ` Alan Cox
2002-03-06 1:45 ` James M.
2002-03-06 16:50 ` Ken Brownfield
2002-03-07 10:11 ` Leonid Mamtchenkov
2002-03-06 23:34 ` Yven Leist
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=20020226072021.GC11837@suse.de \
--to=axboe@suse.de \
--cc=Dieter.Nuetzel@hamburg.de \
--cc=akpm@zip.com.au \
--cc=brownfld@irridia.com \
--cc=linux-kernel@vger.kernel.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