summaryrefslogtreecommitdiff
path: root/drivers/md
diff options
context:
space:
mode:
authorXU pengfei <xupengfei@nfschina.com>2022-08-17 12:21:40 +0300
committerSong Liu <song@kernel.org>2022-09-22 10:05:03 +0300
commit12ba6676b9254bc5a555f1c52f9c0516e86392b7 (patch)
treeb206ab9736679f23f96a733d9223fcbf96b62c45 /drivers/md
parent9713a67067897a9e372c52124f72f8e00b2e6031 (diff)
downloadlinux-12ba6676b9254bc5a555f1c52f9c0516e86392b7.tar.xz
md/raid5: Fix spelling mistakes in comments
Fix spelling of 'waitting' in comments. Signed-off-by: XU pengfei <xupengfei@nfschina.com> Signed-off-by: Song Liu <song@kernel.org>
Diffstat (limited to 'drivers/md')
-rw-r--r--drivers/md/raid5-cache.c6
1 files changed, 3 insertions, 3 deletions
diff --git a/drivers/md/raid5-cache.c b/drivers/md/raid5-cache.c
index f4e1cc1ece43..058d82e7fa13 100644
--- a/drivers/md/raid5-cache.c
+++ b/drivers/md/raid5-cache.c
@@ -1327,9 +1327,9 @@ static void r5l_write_super_and_discard_space(struct r5l_log *log,
* superblock is updated to new log tail. Updating superblock (either
* directly call md_update_sb() or depend on md thread) must hold
* reconfig mutex. On the other hand, raid5_quiesce is called with
- * reconfig_mutex hold. The first step of raid5_quiesce() is waitting
- * for all IO finish, hence waitting for reclaim thread, while reclaim
- * thread is calling this function and waitting for reconfig mutex. So
+ * reconfig_mutex hold. The first step of raid5_quiesce() is waiting
+ * for all IO finish, hence waiting for reclaim thread, while reclaim
+ * thread is calling this function and waiting for reconfig mutex. So
* there is a deadlock. We workaround this issue with a trylock.
* FIXME: we could miss discard if we can't take reconfig mutex
*/