Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <20220718082650.9784-1-wangborong@cdjrlc.com>
In-Reply-To: <20220718082650.9784-1-wangborong@cdjrlc.com>
From:   Ulf Hansson <ulf.hansson@linaro.org>
Date:   Fri, 22 Jul 2022 11:32:38 +0200
Message-ID: <CAPDyKFpBc_XZStRb7mwQ_nN-YUnxxmXrqx6hFFxoVG=iJ-VdiQ@mail.gmail.com>
Subject: Re: [PATCH 1/3] mmc: sdhci-acpi: Fix comment typo
To:     Jason Wang <wangborong@cdjrlc.com>
Cc:     adrian.hunter@intel.com, haibo.chen@nxp.com, shawnguo@kernel.org,
        s.hauer@pengutronix.de, kernel@pengutronix.de, festevam@gmail.com,
        linux-imx@nxp.com, kishon@ti.com, linux-mmc@vger.kernel.org,
        linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Thu, 21 Jul 2022 at 18:30, Jason Wang <wangborong@cdjrlc.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@cdjrlc.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
>