linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Nhat Pham <nphamcs@gmail.com>
To: Colin Ian King <colin.i.king@gmail.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
	Shuah Khan <shuah@kernel.org>,
	linux-mm@kvack.org,  linux-kselftest@vger.kernel.org,
	kernel-janitors@vger.kernel.org,  linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH][next] selftests: Fix spelling mistake "trucate" -> "truncate"
Date: Fri, 5 May 2023 12:01:31 -0700	[thread overview]
Message-ID: <CAKEwX=M8gL=XocVdDuo4NmFgv8_SRu-wvSZqcwxradVqS5kBZg@mail.gmail.com> (raw)
In-Reply-To: <20230505110855.2493457-1-colin.i.king@gmail.com>

On Fri, May 5, 2023 at 4:08 AM Colin Ian King <colin.i.king@gmail.com> wrote:
>
> There is a spelling mistake in a message. Fix it.
>
> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
> ---
>  tools/testing/selftests/cachestat/test_cachestat.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/testing/selftests/cachestat/test_cachestat.c b/tools/testing/selftests/cachestat/test_cachestat.c
> index c3823b809c25..9be2262e5c17 100644
> --- a/tools/testing/selftests/cachestat/test_cachestat.c
> +++ b/tools/testing/selftests/cachestat/test_cachestat.c
> @@ -191,7 +191,7 @@ bool test_cachestat_shmem(void)
>         }
>
>         if (ftruncate(fd, filesize)) {
> -               ksft_print_msg("Unable to trucate shmem file.\n");
> +               ksft_print_msg("Unable to truncate shmem file.\n");
>                 ret = false;
>                 goto close_fd;
>         }
> --
> 2.30.2
>

Acked-by: Nhat Pham <nphamcs@gmail.com>

Thanks, Colin! I'm forwarding this to Andrew.
Andrew, could you fold this misspelling fix into the patch
as well? I think it's this commit in mm-unstable:

f2277ac105b4 selftests: add selftests for cachestat


      reply	other threads:[~2023-05-05 19:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-05 11:08 Colin Ian King
2023-05-05 19:01 ` Nhat Pham [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAKEwX=M8gL=XocVdDuo4NmFgv8_SRu-wvSZqcwxradVqS5kBZg@mail.gmail.com' \
    --to=nphamcs@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=colin.i.king@gmail.com \
    --cc=hannes@cmpxchg.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=shuah@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox