public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
	David Howells <dhowells@redhat.com>
Subject: Re: nfsd 2.6.28 merge plans
Date: Tue, 14 Oct 2008 12:07:53 -0700	[thread overview]
Message-ID: <20081014120753.7f968845.akpm@linux-foundation.org> (raw)
In-Reply-To: <20081008232237.GH14527@fieldses.org>

> On Wed, 8 Oct 2008 19:22:37 -0400 "J. Bruce Fields" <bfields@fieldses.org> wrote:
> Linus's release announcement for -rc9 suggested 2.6.27 could be released
> (and the 2.6.28 merge window opened) any day now.
> 
> What I'm currently planning to merge is the contents of
> 
> 	git://linux-nfs.org/~bfields/linux.git for-2.6.28
> 
> summarized below.
> 
> Chuck's contributed a ton of small patches preparing for ipv6 support
> (which we expect to complete in 2.6.29), Tom Tucker has added support
> for fast memory registration to the server rdma code, and Benny's
> NFSv4.1 work continues to produce miscellaneous NFSv4.1 bugfixes and
> cleanups.
> 
> There's also one pure locking patch, which makes vfs support for posix
> locking configurable.
> 
> And I've got some grace period patches (which I hope will also pave the
> way for nfsd lock migration support in 2.6.29), and some minor tweaks to
> our rpcsec_gss code which (together with recent nfs-utils patches)
> finally makes rpcsec_gss for v2 and v3 work as well as it does for v4.

Thanks.

Is anything happening with David Howells's fscache and cachefiles work over
there?


  reply	other threads:[~2008-10-14 19:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-08 23:22 nfsd 2.6.28 merge plans J. Bruce Fields
2008-10-14 19:07 ` Andrew Morton [this message]
2008-10-14 20:33   ` David Howells
2008-10-14 20:51     ` Trond Myklebust
2008-10-15  9:17       ` David Howells
2008-11-20 14:25       ` 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=20081014120753.7f968845.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=bfields@fieldses.org \
    --cc=dhowells@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.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