From: Benny Halevy <bhalevy@panasas.com>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: pNFS Mailing List <pnfs@linux-nfs.org>,
"J. Bruce Fields" <bfields@citi.umich.edu>,
NFS list <linux-nfs@vger.kernel.org>
Subject: nfs41-for-next
Date: Wed, 01 Apr 2009 15:37:20 +0300 [thread overview]
Message-ID: <49D36000.8030708@panasas.com> (raw)
git://linux-nfs.org/~bhalevy/linux-pnfs.git nfs41-for-next
holds the nfs41-for-2.6.30 patches rebased onto today's
linux-next. Note that nfsd41-for-2.6.30 is already in
linux-next via Bruce's tree so nfs41-for-next provides
both the client and server code for nfsv4.1.
The only material change between nfs41-for-2.6.30 and
nfs41-for-next is that I dropped this patch:
"FIXME: nfs41: sunrpc: handle clnt==NULL in call_status"
from -for-next since it's not strictly needed there
as clnt is nor dereferenced anymore in the -ENOTCONN
case in call_status().
Benny
reply other threads:[~2009-04-01 12:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=49D36000.8030708@panasas.com \
--to=bhalevy@panasas.com \
--cc=Trond.Myklebust@netapp.com \
--cc=bfields@citi.umich.edu \
--cc=linux-nfs@vger.kernel.org \
--cc=pnfs@linux-nfs.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