Commit f1f565a2 authored by Randy Dunlap's avatar Randy Dunlap Committed by Ilya Dryomov

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: default avatarRandy Dunlap <rdunlap@infradead.org>
Reviewed-by: default avatarJeff Layton <jlayton@kernel.org>
Signed-off-by: default avatarIlya Dryomov <idryomov@gmail.com>
parent 3b4168dd
...@@ -839,7 +839,7 @@ static void destroy_caches(void) ...@@ -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). * mount, skipping steps that may hang while waiting for server(s).
*/ */
static void ceph_umount_begin(struct super_block *sb) static void ceph_umount_begin(struct super_block *sb)
......
...@@ -355,7 +355,7 @@ struct ceph_inode_info { ...@@ -355,7 +355,7 @@ struct ceph_inode_info {
unsigned i_dirty_caps, i_flushing_caps; /* mask of dirtied fields */ 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 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 * 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 * requires the mdsc->cap_dirty_lock. List presence for an item can
......
...@@ -58,7 +58,7 @@ ...@@ -58,7 +58,7 @@
* because 10.2.z (jewel) did not care if its peers advertised this * because 10.2.z (jewel) did not care if its peers advertised this
* feature bit. * 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 * RETIRED. This can normally be done in the *next* major release
* following the one in which we marked the feature DEPRECATED. In * following the one in which we marked the feature DEPRECATED. In
* the above example, for 12.0.z (luminous) we can say: * the above example, for 12.0.z (luminous) we can say:
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment