On Fri, Jul 1, 2022 at 6:54 PM Zhang Jiaming <jiaming@xxxxxxxxxxxx> wrote:
>
> There are 2 spelling mistakes in comments. Fix it.
>
> Signed-off-by: Zhang Jiaming <jiaming@xxxxxxxxxxxx>
Applied to md-next.
Thanks,
Song
> ---
> drivers/md/md-cluster.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/md/md-cluster.c b/drivers/md/md-cluster.c
> index 37cbcce3cc66..742b2349fea3 100644
> --- a/drivers/md/md-cluster.c
> +++ b/drivers/md/md-cluster.c
> @@ -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
>
