linux-kernel - Re: [PATCH 1/3] mmc: sdhci-acpi: Fix comment typo

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: <CAPDyKFpBc_XZStRb7mwQ_nN-YUnxxmXrqx6hFFxoVG=iJ-VdiQ@mail.gmail.com>
Date:   Fri, 22 Jul 2022 11:32:38 +0200
From:   Ulf Hansson <ulf.hansson@...aro.org>
To:     Jason Wang <wangborong@...rlc.com>
Cc:     adrian.hunter@...el.com, haibo.chen@....com, shawnguo@...nel.org,
        s.hauer@...gutronix.de, kernel@...gutronix.de, festevam@...il.com,
        linux-imx@....com, kishon@...com, linux-mmc@...r.kernel.org,
        linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 1/3] mmc: sdhci-acpi: Fix comment typo

On Thu, 21 Jul 2022 at 18:30, Jason Wang <wangborong@...rlc.com> wrote:
>
> The double `the' is duplicated in the comment, remove one.
>

Hi Jason, these spelling fixups are getting somewhat annoying to me,
sorry. Don't get me wrong, it's nice to have good readable comments,
but the patches don't really need to be one line of change per patch.
Could you perhaps look over all mmc host drivers and fix all spelling
mistakes in them and send one patch to cover all of them instead?

Kind regards
Uffe

> Signed-off-by: Jason Wang <wangborong@...rlc.com>
> ---
>  drivers/mmc/host/sdhci-acpi.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/mmc/host/sdhci-acpi.c b/drivers/mmc/host/sdhci-acpi.c
> index 4cca4c90769b..bddfaba091a9 100644
> --- a/drivers/mmc/host/sdhci-acpi.c
> +++ b/drivers/mmc/host/sdhci-acpi.c
> @@ -648,7 +648,7 @@ static int sdhci_acpi_emmc_amd_probe_slot(struct platform_device *pdev,
>          *       in reading a garbage value and using the wrong presets.
>          *
>          *       Since HS400 and HS200 presets must be identical, we could
> -        *       instead use the the SDR104 preset register.
> +        *       instead use the SDR104 preset register.
>          *
>          *    If the above issues are resolved we could remove this quirk for
>          *    firmware that that has valid presets (i.e., SDR12 <= 12 MHz).
> --
> 2.35.1
>