From: NeilBrown <neilb@cse.unsw.edu.au>
To: Andrew Morton <akpm@osdl.org>
Cc: nfs@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: [PATCH kNFSd 000 of 3] Introduction
Date: Fri, 13 Jan 2006 14:14:27 +1100 [thread overview]
Message-ID: <20060113141059.4573.patches@notabene> (raw)
Three more assorted nfsd patches.
The last is somewhat embarassing... a previous patch completely left out the
nfsv2 section. This didn't cause compile errors, but completely broke
NFSv2 service... and it was in -mm for at least a month with noone noticing.
[PATCH kNFSd 001 of 3] semaphore to mutex conversion.
[PATCH kNFSd 002 of 3] Fix some more errno/nfserr confusion in vfs.c
[PATCH kNFSd 003 of 3] Provide missing NFSv2 part of patch for checking vfs_getattr.
next reply other threads:[~2006-01-13 3:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-13 3:14 NeilBrown [this message]
2006-01-13 3:14 ` [PATCH kNFSd 001 of 3] semaphore to mutex conversion NeilBrown
2006-01-13 3:14 ` [PATCH kNFSd 003 of 3] Provide missing NFSv2 part of patch for checking vfs_getattr NeilBrown
2006-01-13 3:14 ` [PATCH kNFSd 002 of 3] Fix some more errno/nfserr confusion in vfs.c NeilBrown
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=20060113141059.4573.patches@notabene \
--to=neilb@cse.unsw.edu.au \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
/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