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: <CAPDyKFp30G=x-LmiG+1NFsKaDTZvBU8bfgr9eUsMHiD4Jymotw@mail.gmail.com>
Date:   Mon, 18 Jul 2022 13:37:48 +0200
From:   Ulf Hansson <ulf.hansson@...aro.org>
To:     Jilin Yuan <yuanjilin@...rlc.com>
Cc:     linux-mmc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mmc/core: fix repeated words in comments

On Sat, 16 Jul 2022 at 16:04, Jilin Yuan <yuanjilin@...rlc.com> wrote:
>
>  Delete the redundant word 'it'.
>  Delete the redundant word 'in'.
>
> Signed-off-by: Jilin Yuan <yuanjilin@...rlc.com>

I am fine with picking up patches that fixes spelling mistakes.
However, I would rather see that you go through all spelling mistakes
in the core and send one patch for all of them. It gets easier for me
to manage it in this way.

Kind regards
Uffe

> ---
>  drivers/mmc/core/core.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/mmc/core/core.c b/drivers/mmc/core/core.c
> index 4b70cbfc6d5d..e4a555a2f202 100644
> --- a/drivers/mmc/core/core.c
> +++ b/drivers/mmc/core/core.c
> @@ -56,7 +56,7 @@ static const unsigned freqs[] = { 400000, 300000, 200000, 100000 };
>  /*
>   * Enabling software CRCs on the data blocks can be a significant (30%)
>   * performance cost, and for other reasons may not always be desired.
> - * So we allow it it to be disabled.
> + * So we allow it to be disabled.
>   */
>  bool use_spi_crc = 1;
>  module_param(use_spi_crc, bool, 0);
> @@ -528,7 +528,7 @@ EXPORT_SYMBOL(mmc_cqe_post_req);
>   * @host: MMC host to recover
>   *
>   * Recovery consists of stopping CQE, stopping eMMC, discarding the queue in
> - * in eMMC, and discarding the queue in CQE. CQE must call
> + * eMMC, and discarding the queue in CQE. CQE must call
>   * mmc_cqe_request_done() on all requests. An error is returned if the eMMC
>   * fails to discard its queue.
>   */
> --
> 2.36.1
>

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ