mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Anton Altaparmakov <aia21@cam.ac.uk>
To: Hugh Dickins <hugh@veritas.com>
Cc: David Howells <dhowells@redhat.com>,
	Andrew Morton <akpm@osdl.org>,
	torvalds@osdl.org, Christoph Hellwig <hch@infradead.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add notification of page becoming writable to VMA ops
Date: Tue, 25 Oct 2005 09:49:49 +0100	[thread overview]
Message-ID: <1130230190.8169.21.camel@imp.csi.cam.ac.uk> (raw)
In-Reply-To: <Pine.LNX.4.61.0510250919270.6403@goblin.wat.veritas.com>

On Tue, 2005-10-25 at 09:26 +0100, Hugh Dickins wrote:
> On Tue, 25 Oct 2005, Anton Altaparmakov wrote:
> > On Mon, 2005-10-24 at 20:11 +0100, Hugh Dickins wrote:
> > 
> > There really is quite a difference between mm/*.c in -mm and Linus
> > kernel at present.  Is all this planned to be merged as soon as 2.6.14
> > is out or is -mm just a playground for now with no mainline merge
> > intentions?
> 
> It certainly won't all be merged as soon as 2.6.14 is out, some of it
> has only just got into -mm.  Andrew's current intention is to merge
> the early part of the changes soonish after 2.6.14 gets out, but he's
> not likely to merge it all into 2.6.15.

Ok, sounds good.  As long as they at least start converging...

> But we aren't using -mm as a playground: it is likely to go forward,
> provided it doesn't show regressions of some kind while it's in -mm.

Cool.

> > Just asking so I know whether to work against stock kernels or -mm for
> > the moment...
> 
> I'd recommend -mm for now.

Great, thanks, will do.

> page_mkwrite will want a spell in there too, won't it?

Sure.  But if the other mm changes in -mm were not going forward it
would be a little silly to get page_mkwrite to work there only to have
to rewrite it in order to get it merged...

If Linus really is going to release .14 in the next few days,
page_mkwrite is never going to make it into .15 anyway, no matter
what...  But .16 would be a realistic target I would have thought which
seems to fit in nicely with the plans for -mm.  (-:

Best regards,

        Anton
-- 
Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)
Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK
Linux NTFS maintainer / IRC: #ntfs on irc.freenode.net
WWW: http://linux-ntfs.sf.net/ & http://www-stu.christs.cam.ac.uk/~aia21/


  reply	other threads:[~2005-10-25  8:50 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-09 14:28 page_mkwrite seems broken Hugh Dickins
2005-10-24 15:16 ` what happened to page_mkwrite? - was: " Anton Altaparmakov
2005-10-24 15:36   ` Hugh Dickins
2005-10-24 15:49     ` Anton Altaparmakov
2005-10-24 15:26 ` David Howells
2005-10-24 15:43   ` Anton Altaparmakov
2005-10-24 16:01     ` Hugh Dickins
2005-10-24 19:38       ` Anton Altaparmakov
2005-10-24 20:31         ` Hugh Dickins
2005-10-24 21:18           ` Anton Altaparmakov
2005-10-24 16:23   ` [PATCH] Add notification of page becoming writable to VMA ops David Howells
2005-10-24 19:11     ` Hugh Dickins
2005-10-25  7:59       ` Anton Altaparmakov
2005-10-25  8:26         ` Hugh Dickins
2005-10-25  8:49           ` Anton Altaparmakov [this message]
2005-10-25  9:49     ` David Howells
2005-10-25  9:55     ` David Howells
2005-10-25 10:12     ` David Howells
2005-10-25 13:18     ` [PATCH] Add notification of page becoming writable to VMA ops [try #2] David Howells
2005-11-30 13:58     ` [PATCH] Add notification of page becoming writable to VMA ops [try #3] David Howells
2005-11-30 14:40       ` Miklos Szeredi
2005-11-30 14:50       ` David Howells
2005-11-30 15:20     ` [PATCH] Add notification of page becoming writable to VMA ops [try #4] David Howells
2006-01-11 12:19     ` [PATCH] Add notification of page becoming writable to VMA ops [try #5] David Howells

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=1130230190.8169.21.camel@imp.csi.cam.ac.uk \
    --to=aia21@cam.ac.uk \
    --cc=akpm@osdl.org \
    --cc=dhowells@redhat.com \
    --cc=hch@infradead.org \
    --cc=hugh@veritas.com \
    --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®