Date:   Tue, 20 Sep 2016 12:49:59 +0900
From:   Masanari Iida <standby24x7@...il.com>
To:     corbet@....net, linux-doc@...r.kernel.org,
        linux-kernel@...r.kernel.org, rdunlap@...radead.org
Cc:     Masanari Iida <standby24x7@...il.com>
Subject: [PATCH] [linux-next] Fix double word "the the" in Doc/filesystems

This patch fix typos "the the" found in Documentation/filesystems.

Signed-off-by: Masanari Iida <standby24x7@...il.com>
---
 Documentation/filesystems/autofs4-mount-control.txt | 10 +++++-----
 Documentation/filesystems/directory-locking         |  2 +-
 Documentation/filesystems/overlayfs.txt             |  2 +-
 3 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/Documentation/filesystems/autofs4-mount-control.txt b/Documentation/filesystems/autofs4-mount-control.txt
index 50a3e01a36f8..572f7e6612a6 100644
--- a/Documentation/filesystems/autofs4-mount-control.txt
+++ b/Documentation/filesystems/autofs4-mount-control.txt
@@ -386,8 +386,8 @@ variation uses the path and optionally in.type field of struct args_ismountpoint
 set to an autofs mount type. The call returns 1 if this is a mount point
 and sets out.devid field to the device number of the mount and out.magic
 field to the relevant super block magic number (described below) or 0 if
-it isn't a mountpoint. In both cases the the device number (as returned
-by new_encode_dev()) is returned in out.devid field.
+it isn't a mountpoint. In both cases the device number (as returned by
+new_encode_dev()) is returned in out.devid field.
 
 If supplied with a file descriptor we're looking for a specific mount,
 not necessarily at the top of the mounted stack. In this case the path
@@ -400,7 +400,7 @@ is one or 0 if it isn't a mountpoint.
 If a path is supplied (and the ioctlfd field is set to -1) then the path
 is looked up and is checked to see if it is the root of a mount. If a
 type is also given we are looking for a particular autofs mount and if
-a match isn't found a fail is returned. If the the located path is the
-root of a mount 1 is returned along with the super magic of the mount
-or 0 otherwise.
+a match isn't found a fail is returned. If the located path is the root
+of a mount 1 is returned along with the super magic of the mount or 0
+otherwise.
 
diff --git a/Documentation/filesystems/directory-locking b/Documentation/filesystems/directory-locking
index 4e32cb961e5b..fe38d83bc3de 100644
--- a/Documentation/filesystems/directory-locking
+++ b/Documentation/filesystems/directory-locking
@@ -23,7 +23,7 @@ RENAME_EXCHANGE in flags argument) lock both.  In any case,
 if the target already exists, lock it.  If the source is a non-directory,
 lock it.  If we need to lock both, lock them in inode pointer order.
 Then call the method.  All locks are exclusive.
-NB: we might get away with locking the the source (and target in exchange
+NB: we might get away with locking the source (and target in exchange
 case) shared.
 
 5) link creation.  Locking rules:
diff --git a/Documentation/filesystems/overlayfs.txt b/Documentation/filesystems/overlayfs.txt
index 4de8475e3a04..820203d87f63 100644
--- a/Documentation/filesystems/overlayfs.txt
+++ b/Documentation/filesystems/overlayfs.txt
@@ -163,7 +163,7 @@ rename or unlink will of course be noticed and handled).
 Multiple lower layers
 ---------------------
 
-Multiple lower layers can now be given using the the colon (":") as a
+Multiple lower layers can now be given using the colon (":") as a
 separator character between the directory names.  For example:
 
   mount -t overlay overlay -olowerdir=/lower1:/lower2:/lower3 /merged
-- 
2.10.0.177.ge510a86

Powered by blists - more mailing lists