linux-kernel - [PATCH -next] vfs: fix typos etc. in Documentation/filesystems/mount

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <8a522bc9-5964-7fd7-9920-32920185ffd7@infradead.org>
Date:   Sat, 1 Dec 2018 13:03:45 -0800
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Linux FS Devel <linux-fsdevel@...r.kernel.org>,
        LKML <linux-kernel@...r.kernel.org>
Cc:     David Howells <dhowells@...hat.com>,
        Al Viro <viro@...iv.linux.org.uk>,
        "linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>
Subject: [PATCH -next] vfs: fix typos etc. in
 Documentation/filesystems/mount_api.txt

From: Randy Dunlap <rdunlap@...radead.org>

Fix typos, grammar, missing '_'s in mount_api.txt.

Signed-off-by: Randy Dunlap <rdunlap@...radead.org>
Cc: David Howells <dhowells@...hat.com>
Cc: Al Viro <viro@...iv.linux.org.uk>
---
Also, is this meant to be "baz" or "bar"?

	static const struct constant_table afs_param_keys[] = {
		{ "baz",	Opt_bar },
		{ "dynamic",	Opt_dyn },
	};

 Documentation/filesystems/mount_api.txt |   12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

--- linux-next-20181130.orig/Documentation/filesystems/mount_api.txt
+++ linux-next-20181130/Documentation/filesystems/mount_api.txt
@@ -258,7 +258,7 @@ manage the filesystem context.  They are
  (*) int (*validate)(struct fs_context *fc);
 
      Called when all the options have been applied and the mount is about to
-     take place.  It is should check for inconsistencies from mount options and
+     take place.  It should check for inconsistencies from mount options and
      it is also allowed to do preliminary resource acquisition.  For instance,
      the core NFS module could load the NFS protocol module here.
 
@@ -438,7 +438,7 @@ returned.
  (*) int vfs_parse_fs_param(struct fs_context *fc,
 			    struct fs_parameter *param);
 
-     Supply a single mount parameter to the filesystem context.  This include
+     Supply a single mount parameter to the filesystem context.  This includes
      the specification of the source/device which is specified as the "source"
      parameter (which may be specified multiple times if the filesystem
      supports that).
@@ -533,7 +533,7 @@ The members are as follows:
      used in the values that the ->keys[] array maps to.
 
      It is expected that, for example, two parameters that are related, say
-     "acl" and "noacl" with have the same ID, but will be flagged to indicate
+     "acl" and "noacl" will have the same ID, but will be flagged to indicate
      that one is the inverse of the other.  The value can then be picked out
      from the parse result.
 
@@ -574,9 +574,9 @@ The members are as follows:
      For example:
 
 	static const struct fs_parameter_spec afs_param_specs[nr__afs_params] = {
-		[Opt_autocell]	= { fs_param_is flag },
+		[Opt_autocell]	= { fs_param_is_flag },
 		[Opt_bar]	= { fs_param_is_enum },
-		[Opt_dyn]	= { fs_param_is flag },
+		[Opt_dyn]	= { fs_param_is_flag },
 		[Opt_foo]	= { fs_param_is_bool, fs_param_neg_with_no },
 		[Opt_source]	= { fs_param_is_string },
 	};
@@ -725,7 +725,7 @@ process the parameters it is given.
 
  (*) bool fs_validate_description(const struct fs_parameter_description *desc);
 
-     This is validates the parameter description.  It returns true if the
+     This validates the parameter description.  It returns true if the
      description is good and false if it is not.
 
  (*) int fs_lookup_param(struct fs_context *fc,