From: "Kendrick M. Smith" <kmsmith@umich.edu>
To: linux-kernel@vger.kernel.org, <nfs@lists.sourceforge.net>
Subject: REPOST patch 27/38: SERVER: expand filehandle to 128 bytes
Date: Wed, 14 Aug 2002 16:49:35 -0400 (EDT) [thread overview]
Message-ID: <Pine.SOL.4.44.0208141649100.1834-100000@vanguard.gpcc.itd.umich.edu> (raw)
Expand filehandle to 128 bytes.
--- old/include/linux/nfsd/nfsfh.h Sun Aug 11 22:57:20 2002
+++ new/include/linux/nfsd/nfsfh.h Sun Aug 11 22:58:05 2002
@@ -96,7 +96,7 @@ struct knfsd_fh {
*/
union {
struct nfs_fhbase_old fh_old;
- __u32 fh_pad[NFS3_FHSIZE/4];
+ __u32 fh_pad[NFS4_FHSIZE/4];
struct nfs_fhbase_new fh_new;
} fh_base;
};
reply other threads:[~2002-08-14 20:47 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=Pine.SOL.4.44.0208141649100.1834-100000@vanguard.gpcc.itd.umich.edu \
--to=kmsmith@umich.edu \
--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;
as well as URLs for NNTP newsgroup(s).