Skip to contentSkip to conversation

md: Fix spelling mistake in comments

PATCH Applied Zhang Jiaming 2 participants 2 messages Jul 2, 2022 – Jul 3, 2022 MD RAID

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 md: Fix spelling mistake in comments

There are 2 spelling mistakes in comments. Fix it.

---
 drivers/md/md-cluster.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/md/md-cluster.c +2 -2
index 37cbcce3cc66..742b2349fea3 100644
@@ -40,7 +40,7 @@ struct resync_info {
 
 /* Lock the send communication. This is done through
  * bit manipulation as opposed to a mutex in order to
- * accomodate lock and hold. See next comment.
+ * accommodate lock and hold. See next comment.
  */
 #define		MD_CLUSTER_SEND_LOCK			4
 /* If cluster operations (such as adding a disk) must lock the
@@ -689,7 +689,7 @@ static int lock_comm(struct md_cluster_info *cinfo, bool mddev_locked)
 	/*
 	 * If resync thread run after raid1d thread, then process_metadata_update
 	 * could not continue if raid1d held reconfig_mutex (and raid1d is blocked
-	 * since another node already got EX on Token and waitting the EX of Ack),
+	 * since another node already got EX on Token and waiting the EX of Ack),
 	 * so let resync wake up thread in case flag is set.
 	 */
 	if (mddev_locked && !test_bit(MD_CLUSTER_HOLDING_MUTEX_FOR_RECVD,
Signature · 1 line
2.25.1
maintainer Applied
#1 lore raw
Quoted 4 lines · Zhang Jiaming

There are 2 spelling mistakes in comments. Fix it.

Applied to md-next.

Thanks,
Song

Quoted 29 lines
---
 drivers/md/md-cluster.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/md/md-cluster.c +2 -3
index 37cbcce3cc66..742b2349fea3 100644
@@ -40,7 +40,7 @@ struct resync_info {
 
 /* Lock the send communication. This is done through
  * bit manipulation as opposed to a mutex in order to
- * accomodate lock and hold. See next comment.
+ * accommodate lock and hold. See next comment.
  */
 #define                MD_CLUSTER_SEND_LOCK                    4
 /* If cluster operations (such as adding a disk) must lock the
@@ -689,7 +689,7 @@ static int lock_comm(struct md_cluster_info *cinfo, bool mddev_locked)
        /*
         * If resync thread run after raid1d thread, then process_metadata_update
         * could not continue if raid1d held reconfig_mutex (and raid1d is blocked
-        * since another node already got EX on Token and waitting the EX of Ack),
+        * since another node already got EX on Token and waiting the EX of Ack),
         * so let resync wake up thread in case flag is set.
         */
        if (mddev_locked && !test_bit(MD_CLUSTER_HOLDING_MUTEX_FOR_RECVD,
--

2.25.1