linux-kernel - Re: [PATCH] md: Fix spelling mistake in comments

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAPhsuW42y5JmQPLS59KFYr1GS=LVztyhhbQ1sbB9Ag4ugV1KSA@mail.gmail.com>
Date:   Sun, 3 Jul 2022 08:00:02 -0700
From:   Song Liu <song@...nel.org>
To:     Zhang Jiaming <jiaming@...china.com>
Cc:     linux-raid <linux-raid@...r.kernel.org>,
        open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] md: Fix spelling mistake in comments

On Fri, Jul 1, 2022 at 6:54 PM Zhang Jiaming <jiaming@...china.com> wrote:
>
> There are 2 spelling mistakes in comments. Fix it.
>
> Signed-off-by: Zhang Jiaming <jiaming@...china.com>

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
>