From: jos poortvliet <jos@mijnkamer.nl>
To: ck@vds.kolivas.org
Cc: Con Kolivas <kernel@kolivas.org>,
linux list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
torvalds@osdl.org
Subject: Re: [ck] Re: 2.6.18-rc1
Date: Mon, 10 Jul 2006 23:58:21 +0200 [thread overview]
Message-ID: <200607102358.25756.jos@mijnkamer.nl> (raw)
In-Reply-To: <200607101308.26291.kernel@kolivas.org>
[-- Attachment #1: Type: text/plain, Size: 1224 bytes --]
Op maandag 10 juli 2006 05:08, schreef Con Kolivas:
> 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?
That's what I wonder about. What exactly are the criteria for getting
something in the kernel? People who want it, and someone willing to maintain
it are part of it, I guess... Good design? The Right Thing, The Right Way?
Now I wouldn't say Andrew is 'nobody', and if he objects, that's something for
sure. But he doesn't even object (do you?).
I like swap prefetch, and it works for me. I can patch it in myself, so its
not all that important to me. And its just a small thing. But many small
things...
Jos
[-- Attachment #2: Type: application/pgp-signature, Size: 191 bytes --]
prev parent reply other threads:[~2006-07-10 21:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-10 3:08 2.6.18-rc1 Con Kolivas
2006-07-10 6:55 ` 2.6.18-rc1 Nick Piggin
2006-07-10 21:58 ` jos poortvliet [this message]
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=200607102358.25756.jos@mijnkamer.nl \
--to=jos@mijnkamer.nl \
--cc=akpm@osdl.org \
--cc=ck@vds.kolivas.org \
--cc=kernel@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
all inboxes | Powered by JetHome®