linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Bernd Schubert <bernd.schubert@fastmail.fm>,
	nfsv4@linux-nfs.org, steved@redhat.com,
	linux-kernel@vger.kernel.org, dhowells@redhat.com,
	linux-next@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	rwheeler@redhat.com
Subject: Re: Pull request for FS-Cache, including NFS patches
Date: Sun, 28 Dec 2008 20:07:26 -0800	[thread overview]
Message-ID: <20081228200726.7b7078b4.akpm@linux-foundation.org> (raw)
In-Reply-To: <20081229144533.4a0ab696.sfr@canb.auug.org.au>

On Mon, 29 Dec 2008 14:45:33 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> I ask because it
> reappeared in linux-next today via the nfs tree (merged into that on Dec
> 24 and 25) ...

And that of course means that many many 2.6.28 patches which I am
maintaining will need significant rework to apply on top of linux-next,
and then they won't apply to mainline.  Or that linux-next will not apply
on top of those patches.  Mainly memory management.

Please drop the NFS tree until after -rc1.

Guys, this: http://lkml.org/lkml/2008/12/27/173

  parent reply	other threads:[~2008-12-29  4:07 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8930.1229560221@redhat.com>
     [not found] ` <20081218142420.GA16728@infradead.org>
     [not found]   ` <20081218123601.11810b7f.akpm@linux-foundation.org>
     [not found]     ` <200812190007.34581.bernd.schubert@fastmail.fm>
     [not found]       ` <20081218152616.a24c013f.akpm@linux-foundation.org>
2008-12-19  0:05         ` Pull request for FS-Cache, including NFS patches Stephen Rothwell
2008-12-29  3:45           ` Stephen Rothwell
2008-12-29  4:01             ` Andrew Morton
2008-12-29 14:30               ` Trond Myklebust
2008-12-29 14:54                 ` Ric Wheeler
2008-12-29 23:05                 ` Muntz, Daniel
2008-12-30 18:44                   ` Trond Myklebust
2008-12-30 22:15                     ` Muntz, Daniel
2008-12-30 22:36                       ` Trond Myklebust
2008-12-30 23:00                         ` Muntz, Daniel
2008-12-30 23:17                           ` Trond Myklebust
2008-12-31 11:15                             ` David Howells
2009-01-01  4:11                             ` Muntz, Daniel
2009-01-01  8:09                               ` Arjan van de Ven
2009-01-01 18:40                                 ` Kyle Moffett
2008-12-31  9:49                       ` Arjan van de Ven
2008-12-29 15:01               ` David Howells
2008-12-29  4:07             ` Andrew Morton [this message]
2008-12-29  5:26               ` Stephen Rothwell
2008-12-29 15:04               ` David Howells
2008-12-29 14:26             ` 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=20081228200726.7b7078b4.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=bernd.schubert@fastmail.fm \
    --cc=dhowells@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=nfsv4@linux-nfs.org \
    --cc=rwheeler@redhat.com \
    --cc=sfr@canb.auug.org.au \
    --cc=steved@redhat.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;
as well as URLs for NNTP newsgroup(s).