From: Con Kolivas <kernel@kolivas.org>
To: linux list <linux-kernel@vger.kernel.org>
Cc: torvalds@osdl.org, ck list <ck@vds.kolivas.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: 2.6.18-rc1
Date: Mon, 10 Jul 2006 13:08:23 +1000 [thread overview]
Message-ID: <200607101308.26291.kernel@kolivas.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 636 bytes --]
I see the merge window closed and swap prefetch got bypassed again. I'd like
to believe it was an oversight but far more likely that Andrew remains
undecided about whether it should go in or not.
No bug reports have come from it in 6 months, the code has remained unchanged
for 3 months, it is as unobtrusive as a driver that is not compiled in
when !CONFIGed and there are numerous reports from satisfied users (even ones
that made it to the scary grounds of lkml). The only thing that happens is
Nick keeps threatening to review it over and over and over and....
I'm not sure what else needs to happen?
--
-ck
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2006-07-10 3:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-10 3:08 Con Kolivas [this message]
2006-07-10 6:55 ` 2.6.18-rc1 Nick Piggin
2006-07-10 21:58 ` [ck] 2.6.18-rc1 jos poortvliet
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=200607101308.26291.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=akpm@osdl.org \
--cc=ck@vds.kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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