linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Greg Banks <gnb@sgi.com>
Cc: linux-fsdevel@vger.kernel.org, nfs@lists.sourceforge.net,
	Christoph Hellwig <hch@lst.de>
Subject: [PATCH] exportfs: fix doc types
Date: Fri, 14 Sep 2007 18:03:01 +0200	[thread overview]
Message-ID: <20070914160301.GA6461@lst.de> (raw)
In-Reply-To: <20070914152424.GJ21965@sgi.com>

And here's a patch to fix the typos Greg found:


Signed-off-by: Christoph Hellwig <hch@lst.de>

Index: linux-2.6/Documentation/filesystems/Exporting
===================================================================
--- linux-2.6.orig/Documentation/filesystems/Exporting	2007-09-14 17:59:35.000000000 +0200
+++ linux-2.6/Documentation/filesystems/Exporting	2007-09-14 18:01:41.000000000 +0200
@@ -104,7 +104,7 @@ are exportable by setting the s_export_o
 super_block.  This field must point to a "struct export_operations"
 struct which has the following members:
 
- encode_fh  (optinonal)
+ encode_fh  (optional)
     Takes a dentry and creates a filehandle fragment which can later be used
     to find/create a dentry for the same object.  The default implementation
     creates a filehandle fragment that encodes a 32bit inode and generation
@@ -118,7 +118,7 @@ struct which has the following members:
   fh_to_parent (optional but strongly recommended)
     Given a filehandle fragment, this should find the parent of the
     implied object and create a dentry for it (possibly with d_alloc_anon).
-    May simplify fail if the filehandle fragment is too small.
+    May fail if the filehandle fragment is too small.
 
   get_parent (optional but strongly recommended)
     When given a dentry for a directory, this should return  a dentry for

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2007-09-14 16:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-30 13:17 [PATH 18/19] exportfs: update documentation Christoph Hellwig
2007-09-14 15:24 ` [NFS] " Greg Banks
2007-09-14 16:03   ` Christoph Hellwig [this message]
2007-09-14 16:40     ` [PATCH] exportfs: fix doc types 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=20070914160301.GA6461@lst.de \
    --to=hch@lst.de \
    --cc=gnb@sgi.com \
    --cc=linux-fsdevel@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).