From: Andrew Morton <akpm@osdl.org>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.6-rc1-mm1
Date: Sun, 18 Apr 2004 23:42:14 -0700 [thread overview]
Message-ID: <20040418234214.7bfb5392.akpm@osdl.org> (raw)
In-Reply-To: <20040419062914.GE743@holomorphy.com>
William Lee Irwin III <wli@holomorphy.com> wrote:
>
> On Sun, Apr 18, 2004 at 11:01:31PM -0700, Andrew Morton wrote:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.6-rc1/2.6.6-rc1-mm1/
> > - All of the anonmm rmap work is now merged up. No pte chains.
> > - Various cleanups and fixups, as usual.
> > - The list of external bk trees is getting a little short, due to problems
> > at bkbits.net. The ones which are here are not necessarily very up-to-date
> > with the various development trees.
>
> Okay, the cpumask_arith.h fixes aren't in here. What do I have to do to
> get the bare minimal correctness fixes in this area propagated to mainline?
>
> The important aspect of these is that they're pertinent to small SMP
> systems, for instance, the dual Pee Cee shenanigans with all kinds of pins
> clipped along with all the other things used in larger boxen castrated.
>
I confess to being moderately exhasperated at the amount of talk and
patching going on in the bitmap and cpumask areas. So when your patch
floated past with a terse description which was bristling with ifs, buts
and maybes I decided to take a pass.
If you want to send it again, cc'ing your co-conspirators and imparting some
confidence that this darned thing is actually meandering toward a conclusion,
please feel free ;)
next prev parent reply other threads:[~2004-04-19 6:42 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-19 6:01 2.6.6-rc1-mm1 Andrew Morton
2004-04-19 6:29 ` 2.6.6-rc1-mm1 William Lee Irwin III
2004-04-19 6:42 ` Andrew Morton [this message]
2004-04-19 6:49 ` 2.6.6-rc1-mm1 William Lee Irwin III
2004-04-19 7:06 ` 2.6.6-rc1-mm1 William Lee Irwin III
2004-04-19 18:39 ` bitmap, cpumask_arith (was: 2.6.6-rc1-mm1) Paul Jackson
2004-04-20 21:17 ` Paul Jackson
2004-04-20 21:38 ` William Lee Irwin III
2004-04-19 6:58 ` 2.6.6-rc1-mm1 Nick Piggin
2004-04-19 9:13 ` 2.6.6-rc1-mm1 failure: kmod.o didn't compile with module-less setup Helge Hafting
2004-04-19 9:17 ` Andrew Morton
2004-04-19 15:26 ` 2.6.6-rc1-mm1 (compile stats) John Cherry
2004-04-19 19:25 ` 2.6.6-rc1-mm1 Christoph Hellwig
2004-04-20 1:13 ` 2.6.6-rc1-mm1 Ian Kent
2004-04-20 1:26 ` 2.6.6-rc1-mm1 Andrew Morton
2004-04-21 9:08 ` 2.6.6-rc1-mm1 Christoph Hellwig
2004-04-21 12:31 ` 2.6.6-rc1-mm1 raven
2004-04-21 13:18 ` 2.6.6-rc1-mm1 Christoph Hellwig
2004-04-21 13:34 ` 2.6.6-rc1-mm1 raven
2004-04-21 15:52 ` 2.6.6-rc1-mm1 raven
2004-04-21 16:09 ` 2.6.6-rc1-mm1 Christoph Hellwig
2004-04-21 12:39 ` 2.6.6-rc1-mm1 raven
2004-04-21 13:19 ` 2.6.6-rc1-mm1 Christoph Hellwig
2004-04-21 13:52 ` 2.6.6-rc1-mm1 raven
2004-04-21 14:56 ` 2.6.6-rc1-mm1 Christoph Hellwig
2004-04-21 15:39 ` 2.6.6-rc1-mm1 raven
2004-04-20 14:27 ` 2.6.6-rc1-mm1 raven
2004-04-20 15:06 ` 2.6.6-rc1-mm1 Rik van Riel
2004-04-21 7:37 ` 2.6.6-rc1-mm1 Sean Neakums
2004-04-21 12:16 ` 2.6.6-rc1-mm1 Hugh Dickins
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=20040418234214.7bfb5392.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.com \
/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
all inboxes | Powered by JetHome®