linux-kernel - Re: [PATCH 2/8] mmc-core: Fix a typo in a comment line

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <0813e0b2-a9fa-2066-b572-5875848b556c@rock-chips.com>
Date:   Tue, 10 Jan 2017 16:43:55 +0800
From:   Shawn Lin <shawn.lin@...k-chips.com>
To:     SF Markus Elfring <elfring@...rs.sourceforge.net>,
        linux-mmc@...r.kernel.org, Adrian Hunter <adrian.hunter@...el.com>,
        Harjani Ritesh <riteshh@...eaurora.org>,
        Jens Axboe <axboe@...com>,
        Linus Walleij <linus.walleij@...aro.org>,
        Mike Christie <mchristi@...hat.com>,
        Ulf Hansson <ulf.hansson@...aro.org>,
        Wolfram Sang <wsa+renesas@...g-engineering.com>
Cc:     shawn.lin@...k-chips.com, LKML <linux-kernel@...r.kernel.org>,
        kernel-janitors@...r.kernel.org, trivial@...nel.org
Subject: Re: [PATCH 2/8] mmc-core: Fix a typo in a comment line

On 2017/1/9 5:43, SF Markus Elfring wrote:
> From: Markus Elfring <elfring@...rs.sourceforge.net>
> Date: Sun, 8 Jan 2017 19:05:37 +0100
>
> Add a missing character in the function description.
>

Good catch!

Reviewed-by: Shawn Lin <shawn.lin@...k-chips.com>

> Signed-off-by: Markus Elfring <elfring@...rs.sourceforge.net>
> ---
>  drivers/mmc/core/mmc_test.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/mmc/core/mmc_test.c b/drivers/mmc/core/mmc_test.c
> index e85ef503d7ce..2f838a13a904 100644
> --- a/drivers/mmc/core/mmc_test.c
> +++ b/drivers/mmc/core/mmc_test.c
> @@ -1533,7 +1533,7 @@ static int mmc_test_area_cleanup(struct mmc_test_card *test)
>
>  /*
>   * Initialize an area for testing large transfers.  The test area is set to the
> - * middle of the card because cards may have different charateristics at the
> + * middle of the card because cards may have different characteristics at the
>   * front (for FAT file system optimization).  Optionally, the area is erased
>   * (if the card supports it) which may improve write performance.  Optionally,
>   * the area is filled with data for subsequent read tests.
>


-- 
Best Regards
Shawn Lin