From: "J. Bruce Fields" <bfields@redhat.com>
To: linux-nfs@vger.kernel.org
Subject: nfsd fixes for 2.6.36
Date: Thu, 29 Jul 2010 18:21:19 -0400 [thread overview]
Message-ID: <1280442084-17867-1-git-send-email-bfields@redhat.com> (raw)
I'm thinking about merging the following fixes for 2.6.36; any review
welcome.
--b.
next reply other threads:[~2010-07-29 22:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-29 22:21 J. Bruce Fields [this message]
2010-07-29 22:21 ` [PATCH 1/5] nfsd: bypass readahead cache when have struct file J. Bruce Fields
2010-07-30 8:10 ` Christoph Hellwig
2010-07-30 8:19 ` Bian Naimeng
2010-07-30 8:25 ` Christoph Hellwig
2010-07-30 15:41 ` J. Bruce Fields
2010-07-30 18:30 ` J. Bruce Fields
2010-07-31 18:18 ` J. Bruce Fields
2010-07-29 22:21 ` [PATCH 2/5] nfsd4: don't pretend to support write delegations J. Bruce Fields
2010-07-29 22:21 ` [PATCH 3/5] nfsd4: miscellaneous process_open2 cleanup J. Bruce Fields
2010-07-29 22:21 ` [PATCH 4/5] nfsd4: fix openmode checking on IO using lock stateid J. Bruce Fields
2010-07-29 22:21 ` [PATCH 5/5] nfsd4: share file descriptors between stateid's J. Bruce Fields
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=1280442084-17867-1-git-send-email-bfields@redhat.com \
--to=bfields@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).