ceph: delete repeated words in fs/ceph/

Drop duplicated words "down" and "the" in fs/ceph/.

[ idryomov: merge into a single patch ]

Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Reviewed-by: Jeff Layton <jlayton@kernel.org>
Signed-off-by: Ilya Dryomov <idryomov@gmail.com>

diff --git a/fs/ceph/super.c b/fs/ceph/super.c
index 933f5df5da7dee11d46660bde2d81d6bcde5e0fa..585aecea5cadafa7972cd01110ace9672dc04664 100644 (file)
--- a/fs/ceph/super.c
+++ b/fs/ceph/super.c
@@ -839,7 +839,7 @@ static void destroy_caches(void)
 }
 
 /*
- * ceph_umount_begin - initiate forced umount.  Tear down down the
+ * ceph_umount_begin - initiate forced umount.  Tear down the
  * mount, skipping steps that may hang while waiting for server(s).
  */
 static void ceph_umount_begin(struct super_block *sb)

diff --git a/fs/ceph/super.h b/fs/ceph/super.h
index 2dcb6a90c63667c26a47aac76cfe406ce3eaa852..9001a896ae8c7c9ccad2fc7c410ab2f106906a55 100644 (file)
--- a/fs/ceph/super.h
+++ b/fs/ceph/super.h
@@ -355,7 +355,7 @@ struct ceph_inode_info {
        unsigned i_dirty_caps, i_flushing_caps;     /* mask of dirtied fields */
 
        /*
-        * Link to the the auth cap's session's s_cap_dirty list. s_cap_dirty
+        * Link to the auth cap's session's s_cap_dirty list. s_cap_dirty
         * is protected by the mdsc->cap_dirty_lock, but each individual item
         * is also protected by the inode's i_ceph_lock. Walking s_cap_dirty
         * requires the mdsc->cap_dirty_lock. List presence for an item can

diff --git a/include/linux/ceph/ceph_features.h b/include/linux/ceph/ceph_features.h
index 39e6f4c575800dc7cb3ee542a653c47928081f55..fcd84e8d88f44b073a14fc1de8478df2c3807a28 100644 (file)
--- a/include/linux/ceph/ceph_features.h
+++ b/include/linux/ceph/ceph_features.h
@@ -58,7 +58,7 @@
  *    because 10.2.z (jewel) did not care if its peers advertised this
  *    feature bit.
  *
- *  - In the second phase we stop advertising the the bit and call it
+ *  - In the second phase we stop advertising the bit and call it
  *    RETIRED.  This can normally be done in the *next* major release
  *    following the one in which we marked the feature DEPRECATED.  In
  *    the above example, for 12.0.z (luminous) we can say: