linux-kernel - Re: [PATCH] mmc/host: fix repeated words 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: <CAPDyKFroJgv=47Q2sAn3cT4rgeu3ntk6euxJ7k-ZQOAMQpeteg@mail.gmail.com>
Date:   Thu, 25 Aug 2022 11:49:05 +0200
From:   Ulf Hansson <ulf.hansson@...aro.org>
To:     wangjianli <wangjianli@...rlc.com>
Cc:     jh80.chung@...sung.com, linux-mmc@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mmc/host: fix repeated words in comments

On Tue, 23 Aug 2022 at 16:30, wangjianli <wangjianli@...rlc.com> wrote:
>
> Delete the redundant word 'the'.

Patches that correct spelling mistakes make sense to me. However, I am
no longer willing to pick one patch per spelling mistake, it's just
silly and I feel like I waste my time.

Instead, I suggest you go through all mmc host drivers and fix *all*
of the spelling mistakes in one single patch. The similar can be done
for the mmc core.

Kind regards
Uffe

>
> Signed-off-by: wangjianli <wangjianli@...rlc.com>
> ---
>  drivers/mmc/host/dw_mmc.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/mmc/host/dw_mmc.c b/drivers/mmc/host/dw_mmc.c
> index 581614196a84..7f00d7d7e35e 100644
> --- a/drivers/mmc/host/dw_mmc.c
> +++ b/drivers/mmc/host/dw_mmc.c
> @@ -1363,7 +1363,7 @@ static void __dw_mci_start_request(struct dw_mci *host,
>                  * is just about to roll over.
>                  *
>                  * We do this whole thing under spinlock and only if the
> -                * command hasn't already completed (indicating the the irq
> +                * command hasn't already completed (indicating the irq
>                  * already ran so we don't want the timeout).
>                  */
>                 spin_lock_irqsave(&host->irq_lock, irqflags);
> --
> 2.36.1
>